In fact doesn't really matter at the moment which syntax do you use. Due to backward compatibility reasons, the plugin approach still works, however it's always better to use the new syntax, in which those measures are NowPlaying measures, not plugin measures. But in fact doesn't really matter.Yep... I read about "NowPlaying", which long ago stopped being a plugin and became a Measure... but before rewriting that piece of code accordingly I wanted to get it to work correctly...
As most probably you know, a line preceded by a semicolon means the line is commented out and Rainmeter simply ignores it.thanks for clarifying Balala...
Yep... I read about "NowPlaying", which long ago stopped being a plugin and became a Measure... but before rewriting that piece of code accordingly I wanted to get it to work correctly...
I think this code line threw me to believe the opposite...which is what I wanted to achieve on a first place... if the player was not playing ( Stopped or Paused )... then the scrolling message would be "Paused" or "Nothing Playing" ...Code:
; [Info]; Measure=String; String=[Title] - [Artist] - [Album]; RegExpSubstitute=1; Substitute="^None - None - None$":"Nothing Playing"; OnChangeAction=[!DisableMeasure Position][!UpdateMeasure Position][!UpdateMeter Text][!Redraw][!EnableMeasure Position]; DynamicVariables=1
I didn't pay much attention to the semicolons before each line an automatically took that as another piece of code rainmeter will read...
Palinka Cheers...
Statistics: Posted by balala — Yesterday, 6:27 pm