With WebParser, only use UpdateRate, never UpdateDivider, and put it on the "parent" WebParser measure(s) the ones that actually go out to a remote source with a URL.
I'm not sure why you are complicating things with a low Update in [Rainmeter] and using DefaultUpdateDivider to force most measures to 10 minutes. I suspect you DON'T want to do any of this.
Just set Update=1000 and set UpdateRate on the "parent" WebParser measure(s) to the number of seconds between trips out to the internet.
Set nothing at all on any "child" measures, they don't actually do anything. Their values are set by their "parent" when it is finished. They should be left with the default UpdateDivider=1, so any IfCondition / IfMatch and such on them are evaluated on each skin update. UpdateRate is just ignored by "child" measures. There is never a reason to try and force "child" WebParser measures to only update every 10 minutes.
WebParser measures that are given a value from URL=[SomeParentWebParserMeasure] and use a RegExp to parse that data are still only "child" measures. They are populated by their parent measure, and don't need any UpdateRate or UpdateDivider on them. They can be used like a "parent" by other "grandchild" measures that use the StringIndex data from them, but for timing purposes, they are still just "child" measures. Again, they don't "do" anything remotely.
All of the "timing" is controlled by, and flows from, the "parent" measure that goes out to the remote source. It will get and parse the data and will "push" appropriate values to any "child" measures that reference it. The "parent" is entirely in control.
I'm not sure why you are complicating things with a low Update in [Rainmeter] and using DefaultUpdateDivider to force most measures to 10 minutes. I suspect you DON'T want to do any of this.
Just set Update=1000 and set UpdateRate on the "parent" WebParser measure(s) to the number of seconds between trips out to the internet.
Set nothing at all on any "child" measures, they don't actually do anything. Their values are set by their "parent" when it is finished. They should be left with the default UpdateDivider=1, so any IfCondition / IfMatch and such on them are evaluated on each skin update. UpdateRate is just ignored by "child" measures. There is never a reason to try and force "child" WebParser measures to only update every 10 minutes.
WebParser measures that are given a value from URL=[SomeParentWebParserMeasure] and use a RegExp to parse that data are still only "child" measures. They are populated by their parent measure, and don't need any UpdateRate or UpdateDivider on them. They can be used like a "parent" by other "grandchild" measures that use the StringIndex data from them, but for timing purposes, they are still just "child" measures. Again, they don't "do" anything remotely.
All of the "timing" is controlled by, and flows from, the "parent" measure that goes out to the remote source. It will get and parse the data and will "push" appropriate values to any "child" measures that reference it. The "parent" is entirely in control.
Statistics: Posted by jsmorley — Yesterday, 6:14 pm