The idea of this is that when you need to disable a mouse action for some reason, which can often be the case when you have overlapping meters that both have mouse actions, before you needed to use !SetOption to set the value of the action to either
(disabled), which would turn off a mouse action without allowing the mouse detection to be passed to any meters or the skin "behind it", or
""(cleared), which would remove the mouse action, allowing any mouse detection to be passed to any meters or the skin "behind it".
The problems this caused were three-fold:
1) The different kinds of mouse actions, for instance "click" actions and "over" actions, did not behave consistently when !SetOption was / is used to set those values.
2) When using
to disable a mouse action, the cursor would still change to the "hand" when you are over the meter. The action is still "detected", just doesn't do anything. This could be odd-looking at best, and confusing at worst.
3) In order to "re-enable" the mouse action, it had to be re-created from scratch using !SetOption, which could make for a very long and complicated bang indeed, as well as having complexities with """Magic Quotes""" when the mouse action being defined contained embedded quotes itself, which it most likely will.
Now you can just "disable" or "clear" a mouse action from any meter, meter group, skin, or skin group, and when you want it back again, you simply "enable" it, and it returns to its originally defined functionality.
We have designed this for maximum flexibility. You can change the state of any individual mouse action type, some of them or all of them, on a single meter, a group of meters, the current skin background [Rainmeter] or a group of skins.
Please see the documentation at:
Mouse Action state bangs