/hydrus/ - Hydrus Network

Note Import Options is going to do that very soon. I need to figure out how NIO defaults are going to work (probably the same way TIO does, based on network domain to allow for finicky per-site options as needed) and do some more parsing stuff, and then it should all link together. If you would like to check out what NIO looks like, please hit up network->downloader components->EXPERIMENTAL: check out Note Import Options. Read the help and tooltips, and let me know if it is crazy confusing or if you think I have missed anything simple, obvious, and important.

Downloader creators can also play with note parsing. It isn't linked to anything yet, but you can see how it works. It is pretty simple, just a new Content Parser type. You set the name of the note and parse the text. It'll get washed through the NIO and then applied to the file. The main remaining problem is the parsing system can't yet do multi-line results. I'd like to tackle that in the coming week(s). If you make downloaders, please have a think about what notes if any you would like to parse and what tech I can add to make that easier. However to stop myself going crazy, I have decided for this first version to not allow parsed note names.

full list

- Qt6:
- if available, Qt6 is now the default. specifically, if the QT_API environment variable is not set, the default is now PySide6, and if that is not available, then PySide2 (Qt5). previously, the opposite was true
- fixed a bug in last week's File Import Options default update with the new 'default' FIOs always showing 'new' files on a gallery/watcher highlight. the Presentation Import Options and the check to see if the pending local file domains actually exist now correctly look up the 'default' FIOs
- Qt6 has much better UI scaling support than Qt5 for zooms other than 100%/200%. many Windows users are at 125%/150%, which revealed some pretty ugly thumbnails and thumb banner text in Qt6. thank you for the reports. I did my homework and read up on how this is _supposed_ to work and I have hacked pretty thumbnails at unusual UI scales. it also redraws itself correctly when I move from a 100% screen to a different one at 125%; let me know how you get on. I'm quite pleased
- the media viewer is still slightly borked at >100%. the fix will be slightly different, but I have a plan and hope to have it sorted for next week.
- fixed setting a mouse scroll wheel shortcut in shortcut options in Qt6
- as a reminder, as far as I know, Windows 7 cannot run Qt6. I will be dropping the Qt5 build in a few weeks, so if you are a Windows 7 user, have a think on what you want to do--either stop updating, move hydrus to a newer OS, or run from source on Win 7/Qt5
- .
- note import options and note parsing:
- note parsing is ready in parts. I am rolling them out for feedback from advanced users and hope to link it all up into a working system next week!
- the different 'x import options', previously file and tag import options, and this week adding 'note import options', are now edited through one combined button and dialog. this 'import options' button dynamically adjusts to deal with how many types of import options the importer has and will relabel and tooltip and right-click-menu itself appropriately
- this new button and multi-edit-panel show '(is default)' status in menus and tabs for quick referral
- if you want to play with note import options, check out the new EXPERIMENTAL menu option under _network->downloader components_. read the help and tooltips and let me know if I have missed anything simple, obvious, and important
- I have no default system for Note Import Options set up yet, so I have not added it for real. I will do something domain-based, similar to Tag Import Options.

- I did however write simple note parsing support. any Content Parser can now have a 'note' parsing type, with a note name. downloader creators, please feel free to play with this, although it isn't complicated and isn't plugged in yet. I think we should review what sites have parseable notes and plan for that rather than start implementing for real just yet. the main limitation is that the parsing system can't do multi-line results yet
- I'd like to see if I can get NIO defaults going next week, and this should suddenly all lock into place. multi-line parsing may be easy or a massive pain, I'm not sure yet
- .
- misc:
- added two new checkboxes to _options->files and trash_ to turn off the yes/no confirmation when you copy/move file across multiple local file services
- the 'overwrite this session?' confirmation dialog now says the session name you are overwriting
- fixed a bug where thumbnails were not immediately updating their banner text on changes to the summary generator objects in _options->tag presentation_
- moved the 'focus thumbnail in preview window' checkboxes from 'gui pages' options page to 'thumbnails'
- updated the text and enabled status of the 'BUGFIX: discord DnD' stuff in _options->gui_
- updated the job description texts in the file maintenance dialog, improving formatting and clarifying what happens in each missing/incorrect job, and what 'remove record' means precisely (it leaves no deletion record)
- fixed a bug from last week when trying to edit your default tag import options
- .
- boring note import options cleanup and refactoring:
- moved ClientGUIImport code up to a new hydrus.client.gui.importing module, refactored it into multiple files, and merged in some other edit panels for various import gui
- merged the file/tag import options buttons into one cleverer and cleaner class. changed its update callables into nicer Qt signals. wrote a new tabbed edit panel for it to work with, and replaced all old import option buttons across the program with the new system
- fixed an issue where the 'import options' buttons (now merged) would allow you to set them as 'default' through the right-click menu even when the button was set to not allow defaults (this state occurs in the options dialog, when you _set_ what the defaults are)
- fixed the same when you try to paste default options into the button
- brushed up and completed the note import options object
- wrote a 'edit note import options' panel
- fixed a small thing where the 'string-to-string' list widget wasn't setting the custom 'value' column header name correctly

next week

More of this, I'm afraid! I regret focusing on this for so long, but the work is going well and I want both done properly. I'll see if I can get the media viewer displaying good at >100% UI scale, knock off any other Qt6 problems, and then hammer out Note Import Options defaults so we can actually start parsing real stuff.

 >>/1338/
> I will switch over to Qt6 exclusively in a few weeks, at which point I'll update the help and talk more about your future options, which will be: stop updating the client; move to a newer OS; run in Win7/Qt5 from source
I feel like Hydrus would be better at self sustaining itself if sites, cookies, downloaders, logins, ect. were updated automatically instead of needing to download a whole new client for those sites and scripts to be updated. Sort of like Jdownloader. I mean yeah you could manually update them yourself but it seems like it would be more convenient to have Hydrus pull updated site/scripts from a source.

Unless Qt6 makes a dramatic change to how the scripts work(I don't know much about programing or scripting) then yeah the only options would be to move on to a newer os.

I had a great week making Qt6 work better, including making the media viewer work well at >100% UI scale, and getting the first version of note parsing finished.

The release should be as normal tomorrow.

 >>/1341/
That's the ideal of the next big iteration of the downloader system. You can manually update each object in it now using the UI, but it is super awkward to work with on any large or repeated scale. I'd really like to have the ability to dial up online repositories, like a github folder or whatever, and proper versioning and author/naming of downloaders so the client can check itself if there is an updated version of a downloader. In my mind, I think of it like how most vidya mod managers work, where you can see the new available versions and update with just a couple clicks.

That said, I don't do many updates to the default downloaders any more. Probably one every few months. The updates people will be missing out on if they stay on Win 7 or similar will be the changelog every week.