No, this is not a good idea, because !SetVariable doesn't alter physically a variable, which means that when you set a value for a variable with a !SetVariable bang, the other skin can't see it, unless you're using a proper form of the bang.the Meters are in two different .ini files so they cannot see each other, the closest they come to seeing each other is by reading the same variables in the @resources file.
So, to hide or show a meter existing into another skin, add the name of the config containing the skin in which you want to show or hide the meter. To be honest I'm not entirely sure now how have you structured your skins, however let's see an example. Assuming the meters of the Security meter group are contained into the Skins\MyConfig\MySubConfig1\MySkin1.ini skin and the meters of the Games group are in the Skins\MyConfig\MySubConfig2\MySkin2.ini skin, in the MySkin1.ini you can apply the bangs in the following form> IfFalseAction=[!HideMeterGroup "Security"][!HideMeterGroup "Games" "MyConfig\MySubConfig2"][!Redraw][!Redraw "MyConfig\MySubConfig2"].
See that here:
- [!HideMeterGroup "Security"] - is hiding the meters of the Security group, contained into the current skin (in which the bang is applied).
- [!HideMeterGroup "Games" "MyConfig\MySubConfig2"] - is hiding the meters of the Games group, contained this time not in the current skin, but into the skin belonging to the MyConfig\MySubConfig2 config, whatever that skin is (take care that there might be more skins into the config). Any of them is activated when you apply this bang, all meters having set the group to Group=Games are hidden).
- [!Redraw] - redraws the current config.
- [!Redraw "MyConfig\MySubConfig2"] - redraws the skin of the MyConfig\MySubConfig2 config.
Statistics: Posted by balala — Today, 2:17 pm