balala wrote: ↑March 10th, 2020, 9:30 pm
But I had. Left it running for a longer time, for instance half an hour. After 5 minutes the skin still shows the string, but if you left it for 30 minutes, then yep, the string indeed become "0".
Oh, really? Well, I had no idea that you experienced the same issue, since you didn't mentioned that in your posts. If I knew, I would have let my version run for 30+ minutes, to see if it changes anything. Oh, and converting everything to UCS-2 LE BOM actually made things worse: no text, no 0, only some nasty characters there.
UPDATE: I encountered the same issue, after letting the skins (both the original and the UCS-2 LE BOM converted one) run for like an hour or so. The conclusion is that neither the UTF-16 or using section variables to specifically display the string value of the measure
solve the issue. Thankfully, as I don't use Lua, I'm not even potentially affected, but for sure the OP is. One workaround that I know will work is to drop Lua for this and just parse the local file using WebParser
(and the appropriate CodePage=
in its options). If there will also be writes to that file, using an .ini / .inc like structure might be recommended, since the only native way for Rainmeter to write to a file is using the !WriteKeyValue
bang (which by default expects such a structure). Personally, I used this method for years without problems.