The basic idea in such cases is always the following: you have a variable which controls the position of a meter (or more, doesn't really matter how many are there). For instance in case of your TestSideBar1 .ini skin, an example of such a variable is W2, controlled by the options of the [MeasureSlide2] measure. When you're hovering the mouse over a meter ([MeterItem2] in this case), the MouseOverAction option of the meter is executed, which starts executing the bangs of the Left option, through the ActionList1 option. This bang is executed more times, quickly one after the other, more times, accordingly to the options set into the ActionList1 option. Executing and re-executing this bang leads to increasing the W2 variable.I'm still trying to figure the Math behind that 4 top sliders... Image may be NSFW.
Clik here to view.
Same goes by in invers order, when you're leaving the [MeterItem2] meter. In this case the Right option is executed accordingly to the settings stated into the ActionList2 option.
The idea of this plugin is to can execute bangs more often then what you've set into the Update option of the [Rainmeter] section, for a limited time. Examples can be found either on the help page of the ActionTimer plugin or on jsmorley's post, linked by you previously. Following those examples can help you understanding how the plugin is working and all math behind it.
Statistics: Posted by balala — Yesterday, 10:09 pm
