Yep, agreed on the first paragraph, it's the way WebParser and Substitute work - that's why I mentioned it's a "hypothetical" situation. I have doubts regarding second paragraph though, because as you might remember, I do a TON of such substitutions in my Feeds skin, for similar strings in length (or even longer) and the delay in parsing that is similar with the delay in parsing weather.com.jsmorley wrote: ↑July 29th, 2020, 6:12 pm I agree, and that occurred to me first thing, but it really can't work that way. Substitute does not "change" the value of a measure, but only the string value that is obtained when some other measure "asks for" the string value of the measure. Child measures are not using the string value of the parent measure, and in fact don't "ask for" any value at all. The child measures values are automatically populated by WebParser itself as a part of the plugin functionality.
The other issue is that the entire weather.com site is ginormous, and using RegExpSubstitute on the entire value pretty much brings Rainmeter to its knees...
Anyway, I fixed the thing in my skin as well. I created a variable Q=\\" and just used it (i.e. #Q#) instead of the hardcoded quotes in my other variables that are involved in regexp substitutions, in case they revert the change tomorrow or something. Added ,"\\"":""" to my own "common substitute" variable and that was it. Had to slightly modify my "data" pattern, but the changes were minor.
Apperently we got away easy this time...