Hello, i searched the forum to solve my problem, tried everything i found but didn't work, seemed easy enough but i really don't know what i'm doing wrong. Here's the thing: i want a skin to be used as a button to change a value on another, so that this other skin appears.
This:
There are many ways to be different - there is only one way to be yourself - be amazing at it
The law of averages says what it means; even if you get everything right, you will get something wrong. Therefore; self managing error trapping initiates another set of averages - amongst the errors, some of them will not be errors, instead those instances will appear to be "luck". One cannot complain of the 'appearance' of 'infinite regress of causation', even if it does not have a predictable pattern, only that it requires luck to achieve.
Nilvarno wrote: ↑December 14th, 2019, 10:34 pm
Hello, i searched the forum to solve my problem, tried everything i found but didn't work, seemed easy enough but i really don't know what i'm doing wrong.
When you want to change dynamically such a variable into another skin, you have to use not the path of the according .ini file, but the config. This means that probably the MouseOverAction option of the [MeterButtonImage] meter should be: MouseOverAction=[!SetVariable Menu "1" "2ndBar\GameLauncher"].
Above red is the config of the GameLauncher.ini skin, this is what you have to use in almost all bangs (except probably just !WriteKeyValue, which indeed needs the complete path of the file where you want to write). If you want / have to set dynamically anything into another skin than the current one, you tell Rainmeter where to set that through the Config name, not through the skins .ini file. Because always only one .ini file can be loaded from a config, if you specify the name of the Config, Rainmeter always knows where to make that setting.
I got it now, it works. thanks to both of you!. Anyway it's quite slow, i mean, i takes a couple of seconds for the other skin to appear, is there a way to speed up the process?
Nilvarno wrote: ↑December 15th, 2019, 10:47 am
I got it now, it works. thanks to both of you!. Anyway it's quite slow, i mean, i takes a couple of seconds for the other skin to appear, is there a way to speed up the process?
Yep, probably same way as you did in the KeyDownAction option of the [MeasureToggle] measure you should update the [MeasureMenu] measure when you're hovering the mouse over the [MeterButtonImage] meter. For this you have to add a !UpdateMeasure bang to the previously posted MouseOverAction option: MouseOverAction=[!SetVariable Menu "1" "2ndBar\GameLauncher"][!UpdateMeasure "MeasureMenu" "2ndBar\GameLauncher"].
See that the above !UpdateMeasure bang, beside the MeasureMenu measure name, has one more parameter ("2ndBar\GameLauncher"), the name of the config in which the measure which has to be updated is located.
Nilvarno wrote: ↑December 15th, 2019, 1:45 pm
woah, it's a rocket now! Thank you for solving and teaching me, you are the best. Oh. merry christmas too