My suite has three different color sources and they depend on a variable and a measure to switch between them.
I want to switch color sources from the settings skin.
I am able to set the variable #ColorSource# to 1, 2 and 3 across all skins using: [!SetVariableGroup "ColorSource" "1" "HUD"].
But i cannot update the measure [mColorSource] using this method, [!UpdateMeasureGroup "mColorSource" "HUD"].
I am therefore forced to do: [!UpdateMeasure "mColorSource" "HUD\Launcher1"][!UpdateMeasure "mColorSource" "HUD\Launcher2"][!UpdateMeasure "mColorSource" "HUD\Launcher3"] so on and so forth...
Just seems a bit inefficient that only some bangs would be skin group friendly.
EDIT: Maybe this should be moved to 'Bugs & Feature Suggestions'
You do not have the required permissions to view the files attached to this post.
StArL0rd84 wrote: ↑October 15th, 2020, 4:46 pmI am able to set the variable #ColorSource# to 1, 2 and 3 across all skins using: [!SetVariableGroup "ColorSource" "1" "HUD"].
But i cannot update the measure [mColorSource] using this method, [!UpdateMeasureGroup "mColorSource" "HUD"].
I am therefore forced to do: [!UpdateMeasure "mColorSource" "HUD\Launcher1"][!UpdateMeasure "mColorSource" "HUD\Launcher2"][!UpdateMeasure "mColorSource" "HUD\Launcher3"] so on and so forth...
Just seems a bit inefficient that only some bangs would be skin group friendly.
EDIT: Maybe this should be moved to 'Bugs & Feature Suggestions'
As far as I know, the Group parameter in the !UpdateMeasureGroup refers to a group of measures, and not a group of skins, which is why your attempt doesn't work. My guess is that the absence of the ability to specify a skin group that the update would be applied on has something to do with Rainmeter not having a "built-in" way of knowing which skins (and from which skin groups) are active at a specific moment of time. Variables, on the other hand, might be stored in a more "central" Rainmeter area (e.g. memory?) so setting them on a more global basis is easier.
That being said, have you tried using the * (i.e. "all") parameter in those bangs, when it comes to skins? For example, [!UpdateMeasureGroup SomeMeasureGroup *], or even [!UpdateMeasure mColorSource *], in order to act on all active skins. Assuming unique measure or measure group names (i.e. that don't exist in other active skins), this might work...
EDIT: Sorry, Yincognito beat me again. As usually...
StArL0rd84 wrote: ↑October 15th, 2020, 4:46 pm
I am able to set the variable #ColorSource# to 1, 2 and 3 across all skins using: [!SetVariableGroup "ColorSource" "1" "HUD"].
But i cannot update the measure [mColorSource] using this method, [!UpdateMeasureGroup "mColorSource" "HUD"].
I am therefore forced to do: [!UpdateMeasure "mColorSource" "HUD\Launcher1"][!UpdateMeasure "mColorSource" "HUD\Launcher2"][!UpdateMeasure "mColorSource" "HUD\Launcher3"] so on and so forth...
Just seems a bit inefficient that only some bangs would be skin group friendly.
The purpose of the !UpdateMeasureGroup is to update all measures belonging to a group of measures in the current skin or in a skin specified through the Config (second) parameter of the !UpdateMeasureGroup bang (if the bangs has such a parameter), but not to update a group of measures in all loaded skins belonging to a group of configs. There is no bang for this, the method you've described is the only way to achieve what you want.
Sorry...
StArL0rd84 wrote: ↑October 15th, 2020, 4:46 pm
EDIT: Maybe this should be moved to 'Bugs & Feature Suggestions'
Yeah, you might post this there as well, but to be honest I doubt this will be added.