Code: Select all
[Variables] Ex=2 LC=[!SetVariable Ex (3-[#*Ex*])][!UpdateMeasure *][!UpdateMeter *][!Redraw][!CommandMeasure AT "Stop 1"][!CommandMeasure AT "Stop 2"][!CommandMeasure AT "Execute [#*Ex*]"] [Rainmeter] Update=1000 DynamicWindowSize=1 AccurateText=1 BackgroundMode=2 SolidColor=47,47,47,255 ---Measures--- [AT] Measure=Plugin Plugin=ActionTimer ActionList1=LogEx1 | Wait 10 LogEx1=[!Log "LogEx1: [#Ex]"][!UpdateMeasure *][!UpdateMeter *][!Redraw] ActionList2=LogEx2 | Wait 10 LogEx2=[!Log "LogEx2: [#Ex]"][!UpdateMeasure *][!UpdateMeter *][!Redraw] UpdateDivider=-1 DynamicVariables=1 ---Meters--- [ATTest] Meter=String FontFace=Consolas FontColor=255,255,255,255 Padding=5,5,5,5 FontSize=16 AntiAlias=1 Text="AT Test" UpdateDivider=-1 LeftMouseUpAction=[#LC] DynamicVariables=1
- the log should alternate / toggle between printing and on left click
- the variable only updates starting with the 2nd click in the bang variable, so the log alternates / toggles between printing and , in effect executing the opposite actions in [AT]
- if I make the bang variable, the log yields an error that "#Ex# is unknown in the formula", although it is properly declared and all, basically forcing me to use the nested variable syntax there, although it's not that critical in that place
- if I make in [ATTest], everything works properly in terms of printed results, except the strange behavior related to the previous note
Unrelated to this, but since it happens in the same code I have to mention it, as it drives me crazy: please, please, please, add an option to the Image (or Image related) meters to freaking ignore the errors related to missing images. You can default it to not ignore them, but just give the option to the user to control logging those errors if he wants to. I said it before, and I say it again: there are times when missing image files actually have a purpose in a skin (like in a dock system where you dynamically reuse a 5 image "submenu" to avoid copy pasting dozens of additional meters and each submenu has a different number of "entries", like 2, 0, 3, 5, 1 or something like this; such a system throws errors for images belonging to submenu entries which are already invalid as per the submenu entries count and such) and nobody needs his log window spamming these errors - it makes finding real log messages a very difficult and annoying task: Such similar options already exist in other places (mostly measures, not meters, apparently) in Rainmeter, like LogSubstringErrors in WebParser, IgnoreWarnings in ActionTimer, etc. It doesn't affect backward compatibility, it has no drawback, only positives.