I believe this might be a test case that we missed when Brian was kind enough to provide the ability to retrieve the value of CURRENTSECTION from Lua some time ago, or otherwise a very curious syntactical / parsing bug...
[SkinFolder]\@Resources\S.lua: [SkinFolder]\SI.ini: The Section Index = ... part in the Text option from the above meter is producing the incorrect '0' (printing from Lua gives empty CURRENTSECTION): On the other hand, precisely the same part in the commented Text option is producing the correct '5' (I only swapped the 2nd and the 3rd lines there): Bottom line, the SI() function works, just not if it's the last one in the Text option. Paradoxally, the OV() one works even if it's the last one in the same option. Both functions request the value of CURRENTSECTION from Lua, but the SI() one does it in a FOR statement (though it shouldn't be a problem since the control expressions are only evaluated once before the loop starts). It's possible that this is a consequence of a ... variable number of arguments to the Lua functions, maybe Rainmeter is not properly 'tracking' where the CURRENTSECTION value is used in that case - just guessing here.
P.S. For conveniency in deciphering my abbreviations, I included the (equivalent) "long name versions" of these functions at the top of the script (having the same behavior). If you wonder, it's not about the abbreviations or confusing them with the parameters for section variables, I already checked that.
[SkinFolder]\@Resources\S.lua:
P.S. For conveniency in deciphering my abbreviations, I included the (equivalent) "long name versions" of these functions at the top of the script (having the same behavior). If you wonder, it's not about the abbreviations or confusing them with the parameters for section variables, I already checked that.
Statistics: Posted by Yincognito — Yesterday, 8:33 pm