That thread is relevant, sure... but what you helped newguy sort out there was something I'd already done in my own example in this thread re: toggling a variable using a button. What we're BOTH still after is a way of toggling the highlight state of the button along with the state of the variable as a visual indicator of the variable state. I had also thought of a "hack" like the one newguy came up with (Set SOUNDS=Toggle) but that's really no good.
When I opened this thread, I had hoped that the changes you guys made to @toggle to be able to test regular Set command states extended to @set variables as well. But it appears not to. So I figure this is a feature request that could best be tackled in one or two ways:
One way would be to let @toggle test for @set variables using something like this syntax:
Which fits both mine and newguys needs, and I think also fits in the context of what you did to allow @toggle to test regular Set command states, however:
An explicit 'toggle on/off' capability that would work something like:
...would be more open ended so people could use it in buttons that might not use EITHER any commands that natively affect the button highlight state OR any use of @set variables like newguy and I are using.
I'd be thrilled with either approach - but maybe the first fits better with the current model. At least, it seems to be a natural extension to @toggles ability to test Set commands just like you enabled @ifset to test @set variables where it could previously only test Set command states.