/hydrus/ - Hydrus Network

The new incremental tagging is great and the default was what I needed. The move feature saved me too, because "oldest first" has the tenth image in the set imported first for whatever reason, and it looks like they put the 28th image at the end, forgot to post it whil posting the set. Everything seems to be working and nothing to report, I would love a "move forward/backwards x" popup in the future if practical.

I upgraded my client
464 > 474 > 509 > 529 > 554 > 578
I technically could have skipped 529 since 509 > 554 gave me an error about regenerating missing ratings tables, and I don't use ratings at all (yet), but since it said it was a "serious error" I went ahead and added the extra step anyways. 529 > 554 still gave me a "may or may not be serious" message about some sort of table entries for ratings I think, but since I don't use them, I just went ahead. Other than that, I didn't ignore any warnings aside from the bitrot notice, which led to the path above.

 >>/1651/
I do have one other thing to mention, the page tags are fine but when I open my collection to page through it, it starts oldest-first (so the image correctly tagged page 10). This didn't change when I changed the way I sorted things to something else, it still shows the collection in import time order instead of page order, and the thumbnail is that oldest, page 10, image. Is that just how collections work or do I need to change some setting not available in the files tab?

 >>/1652/
Never mind, it finally occurred to me I can select portions and move them past the single file together instead.

I had a great week back into things. I improved UI quality of life with some better list workflow and regex editing, cut down on import folder inefficiency, and fixed an annoying problem in the known URL checking logic.

The release should be as normal tomorrow.

 >>/1652/
Not sure if I am totally understanding you, but collections have the same internal sort as the outer sort you have set on the page. If you set to sort by import time, collections will sort their internal files by import time and then sort amongst themselves by import time too (usually by something like their minimum held import time, or for metadata that aggregates appropriately, total filesize for filesize). So, if you have paged content collected, I recommend you always sort by 'namespaces->creator-series-volume-chapter-page' kind of thing, and collect-by creator+chapter or similar.

In future I expect I'll add a second sort for collection internals, or an override option, or something, but it is stuck for now.