Oh, I see now - you wanted to avoid excessively polling the site on refresh by the users and instead inadvertently allowed the same because all instances of the skin requested the data at the same minutes every hour based on that Time formula. Yeah, doing a trunc of a Counter measure should indeed distribute requests about the same as non refreshed skins. Coupled with the fact that updates are only approximations of time in Rainmeter given different CPU frequencies and workloads, that should make things better in that regard.Droptop used a trunc of current minute divided by 20 with an OnChangeAction to trigger the webparser update. Eg. at 0 minutes, 20 minutes, and 40 minutes of every hour.
Time measure is used as WebParser would otherwise attempt to update every time the skin is refreshed. Instead the OnChangeAction opens a separate ini that deactivates itself once the parsing is complete. Alternatively I could look into using a trunc of a Counter measure so that users should theoretically parse at all different times of the day.
Personally, if I were to use Nominatim, I'd let the the requests manual, whenever the user changes his location - which would be extremely rare, unless we're talking about people who travel a lot, with their laptop around. If paranoid, I'd also self unload the skin once the user searched once and chose a variant from the results, to prevent intentional clicking to search till the hand hurts. But these are just hypothetical considerations, everyone designs their skin a differently.
Statistics: Posted by Yincognito — Today, 3:22 pm — Replies 15 — Views 263254