Yes - Yes - YesYou just need to put [FinishAction=[!Enablemeasure "cIndex1_PriceCalc"] in the parent measure which is [InfoIndex1] rather than [mIndex1_Price].
[...]
This did it! Argh, I could have seen this myself, of course it needs to go to the initial WebParser measure: No more Calc: Extra operation errors. Price rounding working perfectly with your lua script and thousand separators is remaining. User can adjust number of digits separately per stock meter. Complete success! THANK you Mordasius!
I added another small feature, marking [LabelPrice1] as Hidden=1 and also enabling the meter only after the WebParser has received the data: FinishAction=[!Enablemeasure "cIndex1_PriceCalc"] [!ShowMeter LabelPrice1]
Shall I share my complete, modified revision with you, so that you can upgrade your official skin distribution package with this cool new feature? Unfortunately, I have deleted two columns, deleted the menu bar and changed font/corners/design details, see screenshots above. Furthermore I made quite some code comments/code rework for better readability and switched a few variables between Skinvars.inc / Stockvars.inc and MarketPrices.ini to my "consistency likings". But this is personal preference and this is why I love Rainmeter --> full adjustability of gadgets down to the pixel. Not possible with any out-of-the-box Windows gadgets.
I saw a few more details in the script, such as using "Group=2" in a few measures but no Group bangs being used and I also still plan to add error management with OnConnectErrorAction displaying an error message in case the WebParser download fails. These are things currently in my head... But it's your meter Mordasius, I am thankful for providing this to the community.
Statistics: Posted by emp00 — Yesterday, 8:08 pm