(Alternatively, adding the meter parameter :MeasureName to section variables would be a great addition to Rainmeter and could be a good substitute for this suggestion. Example: [#CURRENTSECTION#:MeasureName] would work.)
Code: Select all
[Rainmeter]
[Variables]
Number=999
[Measure1]
Measure=Calc
Formula=1
[Measure2]
Measure=Calc
Formula=2
[Measure3]
Measure=Calc
Formula=3
;--------------------------------
[MeterStyle]
FontSize=50
FontColor=255,255,255
Text=Click %1
LeftMouseUpAction=[!WriteKeyValue Variables Number %1]
Hidden=(%1 = 1 ? 0 : 1)
;--------------------------------
[Meter1]
Meter=String
MeasureName=Measure1
MeterStyle=MeterStyle
[Meter2]
Meter=String
MeasureName=Measure2
MeterStyle=MeterStyle
Y=R
[Meter3]
Meter=String
MeasureName=Measure3
MeterStyle=MeterStyle
Y=R
Perhaps there is another solution to this problem that I'm not aware of. :MeasureName as a meter parameter would be a great alternative. [#CURRENTSECTION#:MeasureName] would be a superior substitute to %1 in this example.
The reason why I would want to use [#CURRENTSECTION#:MeasureName] instead of calling that measure by name directly is for Styles. Without this feature, multiple meters that have similar actions but use varying measures would need their own unique LeftMouseUpActions. With this feature, all LeftMouseUpActions can be consolidated into one style, drastically reducing the workload.