rbriddickk84 wrote: ↑August 30th, 2023, 6:07 am
I often use "group" bangs in many types, meters, measures, variables sometimes,
Yes, but here we're talking about group of skins, which is another story. See below...
rbriddickk84 wrote: ↑August 30th, 2023, 6:07 am
Also i am often using the "if skin is activated" lookup before i take external actions, but good reminder!
How do you do a "if skin is activated" lookup? By an ActiveConfig plugin measure or did you find another way?
However, strictly related to the question you had, here is a short example. Assuming you want to change a variable (let's name it Something) into the
Skins\illustro\Clock\Clock.ini skin (yes, I know there is no such a variable, but I chose this only to can easier explain). You can use the following option onto any other skin:
LeftMouseUpAction=[!SetVariable Something "12" "illustro\Clock"] (don't take into account the update of the appropriate measures and / or meters inot the Clock.ini skin, nor the redraw of the skin, these are not important from the point of view of what I want to describe). If a skin of the
Skins\illustro\Clock config is active (namely Clock.ini), the bang works well, setting the value. However if the Clock skin (or any other of the named config, if there is any) is not active, you immediately get an error in the log.
Now if you add a
Group=MyClock (or obviously use another name) option to the [Rainmeter] section of the
Skins\illustro\Clock\Clock.ini skin and you alter a little bit the above LeftMouseUpAction for instance to this form:
LeftMouseUpAction=[!SetVariableGroup Something "12" "MyClock"], you never get the error message once again, no matter if the Clock.ini skin is active or not, when you click the meter having set the above LeftMouseUpAction option.
This is an extremely simple solution, which makes not necessary using an ActiveConfig plugin measure (or any other way), to check if the skin in which you want to set the variable, is loded or not.
