Help: Rainmeter Skins • Re: Update=-1 vs Disabled Measure?

I have an old thread adjacent to that which doesn't look into Disabled specifically, but the relevant part from that is this post and maybe more importantly seeing what exactly happens during each update cycle here. Basically the short answer is that, for a handful of measures and meters and any reasonable update rate, it's not going to matter, but to the specifics:

1. Does adding Update=-1 do anything else for performance/resource usage if measures are disabled?

With 10 measures of most any kind, it's not going to make a real difference if you apply Update=-1 if it's already disabled.

2. Is it better to have Update=1000 and not worry about disabling the measures?

Probably yes

3. Is there any difference between the two when it comes to resource usage regarding the measures only, ignore the rest of the skin.

Realistically, no

I do think it's an important topic in the sense that a public use skin with a decent amount of measures and meters should be able to run on older hardware with no performance impact, and it's best to set those details as you go in case it turns into something more complicated, but most of the time it's not going to be an issue. You know most of it I'm sure, but just for general reference:

• Update=1000 is the standard and updates once a second, and unless it's for an audio visualizer or similar, will handle most any situation
• Update=-1 does not normally update after the initial update, but can be manually updated through bangs or other methods
• UpdateDivider=-1 is the same as above but for measures and meters
• Paused=1 will do nothing and skip to next measure on each update cycle
• Disabled=1 will set the number value to 0 on each update and signal if the measure has changed

The difference in resource usage between UpdateDivider=-1, Paused=1, and Disabled=1 is basically inconsequential.

Statistics: Posted by Alex88 — Today, 12:47 am

---