This is intended to allow you to set a low Update rate on a skin, to support animations or other skin elements that need a fast update rate, while not having to manually set an UpdateDivider on a great many other measures and meters that may not require the rapid update.
http://docs.rainmeter.net/manual-beta/skins/rainmeter-section#DefaultUpdateDivider
Example:
Code: Select all
[Rainmeter]
Update=100
DynamicWindowSize=1
AccurateText=1
DefaultUpdateDivider=10
[MeasureSlow]
Measure=Calc
Formula=(MeasureSlow % 100) + 1
[MeasureFast]
Measure=Calc
Formula=(MeasureFast % 100) + 1
UpdateDivider=1
[MeterSlow]
Meter=String
MeasureName=MeasureSlow
MeasureName2=MeasureFast
FontSize=11
FontColor=255,255,255,255
SolidColor=47,47,47,255
Padding=5,5,5,5
AntiAlias=1
Text=%1 : %2
[MeterFast]
Meter=String
MeasureName=MeasureSlow
MeasureName2=MeasureFast
Y=3R
FontSize=11
FontColor=255,255,255,255
SolidColor=47,47,47,255
Padding=5,5,5,5
AntiAlias=1
Text=%1 : %2
UpdateDivider=1
So you may have a skin with 3 measures and meters involved in some animation, and need to set the Update rate of the skin to say "20" to support this. Meanwhile, you may have 100 other measures and meters in the skin that are not involved in the animation. Previously, for the sake of resource efficiency, you would want to set all of them to UpdateDivider=50, so they only update once a second (the normal Update=1000). With this new option, you would set Update=20 and DefaultUpdateDivider=50 in [Rainmeter]. Then you would only need to set UpdateDivider=1 on the 3 measures and meters for the animation. The 100 other measures and meters are already set properly by default.
On the other hand, if you have a skin with 100 measures and meters involved in the animation, and 3 there are not, then don't set DefaultUpdateDivider, and just set UpdateDivider=50 on the 3 measures. The question you want to ask is "what saves me the most copy and pasting?"
While DefaultUpdateDivider is in the [Rainmeter] section and thus cannot be dynamically changed, individual UpdateDivider options on measures and meters of course can.
One small caution I would offer is that measures that use UpdateRate to internally track how often they perform some action will almost always be set with an UpdateRate (default 300) and no UpdateDivider. This is particularly true of WebParser parent measures, and also Ping. It is really best, from a timing standpoint, to use UpdateDivider=1 with WebParser, and set UpdateRate to control them.