Iirc death.crafter advised me against that method and said it's a better idea to follow your suggestion here. So I have tried to do that instead. I also find it easier to read the code that wayYincognito wrote: ↑September 12th, 2024, 11:22 pm Does this work and not confuse Rainmeter? Cause if it doesn't, [#[#CURRENTSECTION]] might be a more "standard" way to write it, via the nested syntax...
It is currently October 4th, 2024, 12:04 am
MeasureStyle
-
- Posts: 1821
- Joined: February 17th, 2011, 7:45 pm
- Location: a Galaxy S7 far far away
Re: MeasureStyle
57686174 77696C6C 6265 77696C6C 6265
-
- Rainmeter Sage
- Posts: 8324
- Joined: February 27th, 2015, 2:38 pm
- Location: Terra Yincognita
Re: MeasureStyle
Yeah, it's clearer this way - in any case, I suspect the [##CURRENTSECTION#] works simply because it's only the 1st nesting level. I imagine that more complex nesting scenarios would require "proper" syntax anyway, so better to keep that syntax consistent in all scenarios. It's easier for the user too, he doesn't have to wonder whether it'll work or not and wil be certain that it will.
-
- Developer
- Posts: 2736
- Joined: November 24th, 2011, 1:42 am
- Location: Utah
Re: MeasureStyle
I just wanted to make a note here about [##CURRENTSECTION#]. While this works, it really isn't a good idea to mix variables using regular syntax vs nested syntax. They are parsed at different times, and you may get unexpected results depending on "where" you place them.
-Brian
I touched on this here: https://forum.rainmeter.net/viewtopic.php?p=215579#p215579
-Brian
I touched on this here: https://forum.rainmeter.net/viewtopic.php?p=215579#p215579