Apologies if I missed a prior thread on this topic.
Does @label work with a three-button? Seems like the label for the overarching three-button itself does not allow it, similar to a standard toolbar label.
I wondered about this myself. When I considered it for a while, I came up with this logic - or so it seems logical for me,
With a three button button you can use the LMB, the RMB and the MMB.
You could use only the LMB in the three button button but this would unnecessary since you could use just a button.
If you use all three mouse buttons, you are probably taking action on three related things - like- copy the timestamp of a file, paste a timestamp into a file, or paste a current timestamp into a file. So, you're taking actions on three things and you can see the results right away. You are not choosing between two things.
If you are using two of the three mouse buttons, you could be doing two related actions as was the case for using all three buttons. But, you are more likely choosing between things - like an Opus setting that has two options with the LMB on one setting and the RMB on the other. If you used the button enough you wouldn't need to look at the button. You would just remember LMB for this, RMB for that. If you only had one such button, this would be no problem as you could easily remember which mouse button did what, But if you had ten such buttons, you might be hard pressed to remember what the LMB did for each one.
This is where a single button that toggles and uses a @Label is handy. When you hover over the single button it reads, e.g., NAV Lock On or NAV Lock OFF. And, this is helpful because you can't tell the NAV Lock status just by looking at he file display.
Here is a shell for the code for such a single button:
Thanks for the response. Although this does not match my use case, it is educational. Your logic makes sense.
As I understand it and have used it to date, one can accomplish 9 actions with a single three-button and a combination of @keydown modifiers (none, ctrl, shift). These actions do NOT have to be related; they just have to make sense to the user.
I am interested in accomplishing a 10th "action" with the three-button by using the @label to identify existing DOpus system information in the three-button's main label using the Sysinfo Evaluator function.
Is this now possible, or a feature for the team to add