Maybe cosmetic, but should also work in usercommands (needs to be added manual when using uc).
...and maybe I misunderstood, but for me it enables no selection
User commands don't go directly on toolbars so I'm not sure what @disablenosel would do in them?
That's not true, Leo. The idea of usercommands is storing complete commands, which you can simply drag into a toolbar when needed and w/o the need modifying or adding commands to the button again. They include everything from description, hotkey up to desired icon, so why not "not selectable" if this is the desired behaviour for the usercommand (button)?
For example this usercommand:
@disablenosel
Copy COPYCREATIONTIME=yes COPYTIME=yes
You have "DO completely stored in your brain", you're part of it (really) - I'm just an user! I save/store all my commands in usercommands (some of them were used once a year). So if I would use the above mentioned command a few months later I surely wouldn't remember to add "@disablenosel" manually to the button, which is also not practicable.
If you're doing that to archive them, it might be better to save them in .dcf files instead. (Just drag a normal button from the toolbar to a folder to create a .dcf file out of it.) Then commands you aren't using won't get in your way when using the command editor, but you can still drag them back to your toolbar if you want to use them again in the future, and they'll be re-created exactly as they were, not as a button which runs another command indirectly like with user-commands.
Why do so many of them need to override the @disablenosel stuff? (e.g. A copy command won't do anything useful when nothing is selected, so I don't understand the example command you gave. Why do you want @disablenosel in that at all?)
Well, I use 90% of the commands from 40 or so, usercommands are absolutely perfect for me - can easily be updated/changed and are good sorted (all begin with "uc_").
I want "@dis..." because you brought the idea . Really, either all affected buttons were disabled on no-selection or none, everything else doesn't make sense, because the toolbar really looks and feels "unlogical" and irritating then! For example the command mentioned above is the third one in copy-button (copy, copy-as, copy-date), which enables them without "@dis..." while all other (move, rename,...) are deactivated by default.
In my opinion the idea is great, but not consequently realized and feels a bit "beta", some default-commands are still selectable.
But alternatively... is there an option to completely disable no selection (sorry for question, I am not yet familiar with all the changes done the last time)
The underlying thing here is that when you drag a user command to a toolbar, it creates a button which runs that user command, by name.
What you want is for it to create a button which is a copy of what's inside that user command, but that is not how it works and is not what user commands are for.
If you store your commands in .dcf files instead then they will behave as you want them to.