windows
zip: https://github.com/hydrusnetwork/hydrus/releases/download/v413/Hydrus.Network.413.-.Windows.-.Extract.only.zip
exe: https://github.com/hydrusnetwork/hydrus/releases/download/v413/Hydrus.Network.413.-.Windows.-.Installer.exe
macOS
app: https://github.com/hydrusnetwork/hydrus/releases/download/v413/Hydrus.Network.413.-.macOS.-.App.dmg
linux
tar.gz: https://github.com/hydrusnetwork/hydrus/releases/download/v413/Hydrus.Network.413.-.Linux.-.Executable.tar.gz
source
tar.gz: https://github.com/hydrusnetwork/hydrus/archive/v413.tar.gz
I had an ok week. I mostly fixed bugs to make a 'clean' release before I go for the tag parents database cache.
It is all misc work this week, no highlights.
full list
- added 'sort by number of files in collection' file sort type. it obviously only does anything interesting if you are collecting by something
- when you enter a tag from a manage tags suggested tags column with a double-click, the tag input box is now immediately focused. entering it with a keyboard action does not move the focus
- wrote a new routine for the 'check and repair' database menu that scans for and fixes invalid tags. this might be some system:tag that snuck in, superfluous unicode whitespace, or some weird website encoding that results in null characters, or any other old tag that has since become invalid. tag translations are written to the log
- added an experimental 'post_index' CONTEXT VARIABLE to subsidiary page parsers–whenever a non-vetoed post has pursuable URLs, this value is incremented by one. this is an attempt to generate a # 0,1,2,3 series. feedback on this would be appreciated, so I can formalise and document it
- added 'no_proxy' option for the options->connection page. it uses comma-separated host/domains, just like for curl or the NO_PROXY environment variable. it defaults to 127.0.0.1. in future, options will be added to auto-inherit proxy info from environment variables
- fixed an error when subscriptions try to publish to a page name when a 'page of pages' already has that name
- activated some old 'clean url' parsing tech I wrote but never plugged in that helps parsing urls from source fields on sites that start with non-url gubbins
- fixed the v411->v412 update step to account for a tags table that has duplicate entries (this shouldn't ever happen, but it seems some legacy bug or storage conversion indicent may have caused this for some users). if a unique constraint error is raised, the update step now gives a little message box and does dedupe work
- fixed an issue where the 'will display as' tag was rendering without namespace when 'hide namespace in normal views' was on
- fixed a recent character encoding routine that was supposed to filter out null characters
- fixed some UPnP error reporting
- _may_ have fixed an odd and seemingly rare 'paintevent' issue when expanding the popup toaster from collapsed state–it may also have been a qt bug, and fixed in the new qt:
- updated qt to 5.15.1 for windows and linux builds. it fixes a couple of odd issues like 'unclicking' to select a menu item (issue #296)
- added session save to holistic ui test suite
- misc code cleanup
- .
- client api:
- wrote a client test for the help menu so I can test some basic functions holistically, hoping to stop some recent typo bugs from happening again
- did a couple of hotfixes for v412 to deal with some client api url pending bugs. the links in the 412 release now point to new fixed builds
- fixed an issue setting additional tags via the client api when the respective service's tag import options are not set to get anything
- fixed a 500 error with /add_tags/add_tags when a tags parameter is an empty list
- fixed the /manage_pages/get_page_info client api help to show the 'page_info' key in the example response
next week
I am now going to write the tag parents database cache. This will basically be the same as I just did for tag siblings, making parents applicable cross-service and completely virtual. I will also improve how the application works, making it pause/resumable in non-interrupting parts in the background, like how repository tag processing works now.
I expect this to take two weeks, possibly three, so please do not expect a release next week. I'll make an update on Tuesday evening as normal.