I built 3 connected queries for a weather widget. IP Location, city -> Weather.com code for city -> Weather.com query.
The problem is that this setup works only on the first load. Eg. when I right click/refresh there is no value, and I can't debug where it gets stuck. I sometimes managed to consistently crash Rainmeter with this.
Is there some error? Is there a better pattern for this setup?
poisonborz wrote: ↑October 28th, 2018, 1:01 pm
I built 3 connected queries for a weather widget. IP Location, city -> Weather.com code for city -> Weather.com query.
The problem is that this setup works only on the first load. Eg. when I right click/refresh there is no value, and I can't debug where it gets stuck. I sometimes managed to consistently crash Rainmeter with this.
Is there some error? Is there a better pattern for this setup?
Instead of setting an UpdateRate=-1 option on parent WebParser measures ([WeatherCode], [MeasureWeatherNow] and [MeasureWeatherForecast]) better disable them adding a Disabled=1 option to each of them, then enable and update each of them when the previous measure gets the values.
So:
Add a Disabled=1 option to [WeatherCode], [MeasureWeatherNow] and [MeasureWeatherForecast] measures.
Remove all UpdateRate=-1 options.
Add the following FinishAction options to the appropriate measures:
balala wrote: ↑October 28th, 2018, 2:26 pm
Instead of setting an UpdateRate=-1 option on parent WebParser measures ([WeatherCode], [MeasureWeatherNow] and [MeasureWeatherForecast]) better disable them adding a Disabled=1 option to each of them, then enable and update each of them when the previous measure gets the values.
Yeah, it now works also on forced refreshes - and is also more efficient! Thanks a lot for looking through the code!
(As for Rainmeter, it's still a bit unsettling that it crashes when 2-3 webparsers start at the same time)
poisonborz wrote: ↑October 28th, 2018, 6:48 pm
(As for Rainmeter, it's still a bit unsettling that it crashes when 2-3 webparsers start at the same time)