Well, based on the report and the code (didn't have the time to test the latter or find other possible workarounds yet, but will do once I get the chance), it works just fine if placed in the Text option, even though it's more or less the same internal process / loop.What is happening is while the meter is first setting up, it calls a custom lua function (from your MeterStyle). This function in turn calls the same meter's GetOption function, which in turns parses the MeterStyle of the same meter.....which in turn calls the lua script again....and again and again.
[...]
It might only effect the MeterStyle option, but I am not sure about that.
This is why I originally thought it might have something to do with the meter style "actively building / importing the options of that meter", something that also can potentially change the structure of the referenced meter, e.g. the number of options in it (directly affecting GetOption() and its own internal FOR / WHILE loop in the process). Most of the other options besides MeterStyle (including the Text option) don't do the latter, sticking with changing only their own contents and sometimes the contents of other options, and this (or the timing of various options) might explain why it works when the Lua function is called from them. Just a supposition, of course, you know best the internal particularities of the Rainmeter code.
Statistics: Posted by Yincognito — Today, 9:37 am — Replies 4 — Views 127