MourningStar wrote: ↑July 29th, 2021, 10:16 pm
Another observation in the ini file. I notice that the [Variables} section is at top/the first lines of code. In other skins it is farther down. Originally I thought first was metadata then rainmeter then ... iow it seemed to me there was 'an order to things'. When I did the rearranging the skin broke so I quickly put Humpty back together again. It just weirded me out.
Yes, I know in other skins is farther down, but personally I don't do things just because everybody else does it or someone else says or recommends it that way - I prefer to follow the logic of things. I like to put [Variables] at the top because all the other sections - including [Rainmeter] and why not, [Metadata] in some cases - use the data there and depend on it (so, from that POV, the variables come "first"), while the section and its contents doesn't depend on any other section, only through "back-reference", so to speak. So, when you set a variable to 3 in [Variables], it's at first 3 and only then other sections can alter it.
That being said, I'm not sure why things "broke" when you attempted rearranging that - maybe because of the @Includes, whose place actually matters (just like for meters). Since we're at it, the place for @Include2=#@#WeatherComJSONMeasures.inc
should have been just before any measure and not necessarily in [Variables], but then, if it didn't produce any side effects, I skipped that.
Regarding the order of things in a skin, Rainmeter is pretty forgiving at that, but there are some elements where the order actually matters. As far as I know (hopefully I'm not mistaken), there isn't a specific order for the main sections in a skin, the whole order of things is logically more about dependencies, with stuff that depend on others in the workflow preferably (but not necessarily) coming last. A developer might be more on point regarding these things, since I never really tried another order than what I use (helping folks doesn't count here, because apart from some special cases, my focus was more on a solution than ordering their code).
Oh, and you're welcome - I'm glad you enjoyed the ride, hopefully it will serve you well for future Rainmeter coding.