JelleDekkers wrote: ↑
April 20th, 2019, 4:47 pm
I thought variables weren't being resolved inside of [Variables]? If they weren't, I wouldn't be "using" the variables before they are defined.
Also, if the order does matter, I suggest the variables in the log window are ordered the way they are read. And make them case-sensitive, just like the measures. You're not going to tell me measures are case senstitive, are you?
I was wrong when I told you in IRC that the order of things in [Variables] doesn't matter. Clearly it does. That's not a bug, it's perfectly logical, just a bit of a surprise to me. Oh well, you live and learn.
I doubt that we are going to change how variables are displayed in About / Skins. They are lower case as when they are read by Rainmeter, they are pretty much instantly converted to lower case, and that is how they are carted around in memory. This is to eliminate issues with the fact that while Rainmeter is case-insensitive, C++ most assuredly isn't. Also, since Variables can be defined, or re-defined, at any time anywhere in the skin using Bangs, this would make it difficult indeed to order them in any logical way other than alphabetical.
Measures are a bit different, since they can only be defined once, when the skin is read on load or refresh, in the order they are in the skin.
Brian may want to weigh in, but I don't see this as an issue we would want to spend a lot of time on.