>>14216
That's the hope. It'd be nice to have some sort of .txt import/export, and mass import/export with an external Hydrus Notes Archive and a new 'notes migration' panel, and Client API access for notes. I hope to slowly push on this in future normal weekly work.
>>14217
>>14231
>>14243
The server is still up. Some weird dude got upset and started spamming TOS-violation stuff to the server along with some friends, so the old invite url got turned off. Assuming the users who run the discord server are ok at that point about putting a new invite up, I'll fold the new on into 397 and all my help links.
>>14219
>>14223
>>14246
Thanks. I agree. The reason for that sibling hard-replace change was because the text on those menu items was too long, and it was getting text…elided in a way where you couldn't see the difference between the two options. I split it up as a quick patch so users (particularly new users) could actually read the difference.
And I totally agree on the super nested thumbnail menus. There are an increasing number of commands in hydrus now, and for things like the duplicates system the available menus are flexible depending on the thumb or selection status, so you can get annoying stuff like in your image with a submenu with only one submenu item, just wasting space and time.
I am happy that that big thumbnail menu is now listed essentially by verb, so it isn't the hacked-together mess that it was, but now it lists many common actions at the same depth as uncommon.
My current plans are:
1) Improve shortcut action support, so if you want to do something often, you can map a key to it and bypass the menu entirely.
2) Clean up my menu code so it is less hardcoded and more unified, modular, and dynamic, so it is less work for me simply to work on it.
3) Hang more options and layout options on the menu code so users in advanced mode get different and briefer labels and layouts.
4) Once it is
really modular, start work on actual menu customisation, as
>>14246 says, so I can have a complicated options panel somewhere where you can turn menu items on and off and manage submenus and so on. I can't do this now, as most menus are hardcoded, and complete customisation would be a hellscape to implement.
This stuff is often difficult for me to notice, especially as different users use different actions to me just in normal usage. Simple feedback on what works and what doesn't is really helpful. For that parent/siblings hard-replace, I can think of a couple of options:
I could collapse the menu into a single 3/4 high one, with a non-functional title label:
hard-replace sibs and add parents (label, maybe in bold, does nothing)
-
just for this service
for all services
Or I could skip the menu entirely and launch a mini-dialog from the button with the explainer text and two buttons for single/all.
As someone who uses this a lot, what do you think you would like? Do you have another idea? What other menus do you find annoying?