[BUG?] Delay bang in OnRefreshAction's nested variable
Posted: June 25th, 2021, 9:46 am
Test skin:
Result: none of the first 3 OnRefreshAction lines work as expected (i.e. delay happening between its adjacent bangs); the last 3 OnRefreshAction lines work as expected, but then they either use plain variables or don't have anything after the nested delay variable
Additional info: the delay seems to want to happen only as the last "instruction" or something
Expected behavior: I want the 1st OnRefreshAction line to behave exactly like the 4th one, as otherwise OnRefreshAction doesn't have a problem with nested variables since the end message nested variable works on its own
So, is it a bug? Can it be fixed?
Code: Select all
[Variables]
DelayDuration=3000
EndMessageIdx=1
StartDelay0=
StartDelay1=[!SetOption DummyMeter SolidColor "0,0,0,255"][!UpdateMeter DummyMeter][!Redraw][!Delay #DelayDuration#][!SetOption DummyMeter SolidColor "255,0,0,255"][!UpdateMeter DummyMeter][!Redraw]
EndMessage0=
EndMessage1=[!Log "End of a #DelayDuration# ms delay"]
[Rainmeter]
Update=1000
DynamicWindowSize=1
AccurateText=1
BackgroundMode=2
SolidColor=47,47,47,255
OnRefreshAction=[!Log "Start of a #DelayDuration# ms delay"][#StartDelay[#EndMessageIdx]][#EndMessage[#EndMessageIdx]]
;OnRefreshAction=[!Log "Start of a #DelayDuration# ms delay"][#StartDelay1][#EndMessage[#EndMessageIdx]]
;OnRefreshAction=[#StartDelay[#EndMessageIdx]][#EndMessage[#EndMessageIdx]]
;OnRefreshAction=[!Log "Start of a #DelayDuration# ms delay"]#StartDelay1#[#EndMessage[#EndMessageIdx]]
;OnRefreshAction=[!Log "Start of a #DelayDuration# ms delay"][#StartDelay[#EndMessageIdx]]
;OnRefreshAction=[#StartDelay[#EndMessageIdx]]
---Meters---
[DummyMeter]
Meter=Image
W=100
H=100
SolidColor=255,0,0,255
Additional info: the delay seems to want to happen only as the last "instruction" or something
Expected behavior: I want the 1st OnRefreshAction line to behave exactly like the 4th one, as otherwise OnRefreshAction doesn't have a problem with nested variables since the end message nested variable works on its own
So, is it a bug? Can it be fixed?