UpdateDivider lower than Update rate possible ?

[kyriakos876]

So I had a problem and the easiest way to solve it is by updating a measure twice or more in every cycle.
For example

Code: Select all

[Rainmeter]
Update=1000

[SomeMeasure]
Measure=...
UpdateDivider=(1/2)
Or
UpdateDivider=(2^(-1))

But none of these work and it just acts like it's UpdateDivider=1 I read in the docs that the program calculates the update rate of a measure by doin (Update*UpdateDivider) so I assume only valid numbers are -1,1,2,3...n right? If that is the case, is there any way to make a measure update faster than the other skin?
Thanks.

[jsmorley]

No. The Update option in [Rainmeter] is the driver. It must be a positive whole number or -1, which has a special meaning of "only once".

The way it works is that you set Update to the "fastest" thing you need regularly updated in the skin, and then set UpdateDivider on each measure / meter that doesn't need to be that fast, or use DefaultUpdateDivider and then set UpdateDivider=1 on just the "fast" ones. In any case, nothing can ever have a normal update cycle faster than the value of Update in [Rainmeter].

[kyriakos876]

No. The Update option in [Rainmeter] is the driver. It must be a positive whole number or -1, which has a special meaning of "only once".

The way it works is that you set Update to the "fastest" thing you need regularly updated in the skin, and then set UpdateDivider on each measure / meter that doesn't need to be that fast, or use DefaultUpdateDivider and then set UpdateDivider=1 on just the "fast" ones. In any case, nothing can ever have a normal update cycle faster than the value of Update in [Rainmeter].

Ok so will set a lower update in rainmeter and add UpdateDivider to every other measure exept the one I want to update faster.
One more thing. How does Rainmeter as a program executes bangs? Say I have

Code: Select all

[SomeMeter]
Meter=Button
....
LeftMouseUpAction=[!Bang1][!Refresh][!Bang2]

Does it read the whole line and then executes all of them or it executes them when it reads? Would anything after the [!Refresh] happen or would it refresh as it reads the command making any other bag after completely useless?

[balala]

But none of these work and it just acts like it's UpdateDivider=1 I read in the docs that the program calculates the update rate of a measure by doin (Update*UpdateDivider) so I assume only valid numbers are -1,1,2,3...n right? If that is the case, is there any way to make a measure update faster than the other skin?
Thanks.

The value of the UpdateDivider must be integer, but there could be another approach. Reduce the value of Update (into the [Rainmeter] section) to half of the initial value (to have the duble update frequency, eg using Update=500, instead of the default Update=1000). Then add to the same [Rainmeter] section, an appropriate DefaultUpdateDivider value (in the above example, add DefaultUpdateDivider=2). This way, the meters and measures will be updated on each Update*DefaultUpdateDivider period, so once per second.
Now add an UpdateDivider=1 option to the "incriminated" section. This option will override the default update set with the DefaultUpdateDivider option, having almost the same result as if you'd use subunitary UpdateDivider value on the section.

[jsmorley]

Ok so will set a lower update in rainmeter and add UpdateDivider to every other measure exept the one I want to update faster.
One more thing. How does Rainmeter as a program executes bangs? Say I have

Code: Select all

[SomeMeter]
Meter=Button
....
LeftMouseUpAction=[!Bang1][!Refresh][!Bang2]

Does it read the whole line and then executes all of them or it executes them when it reads? Would anything after the [!Refresh] happen or would it refresh as it reads the command making any other bag after completely useless?

Both bangs would be executed. The entire line is "parsed" and everything is executed in it.

LeftMouseUpAction=[!Log "1"][!DeactivateConfig][!Log "2"]

Even with that, both !Log bangs would happen, even though the skin is unloaded between them.

[kyriakos876]

The value of the UpdateDivider must be integer, but there could be another approach. Reduce the value of Update (into the [Rainmeter] section) to half of the initial value (to have the duble update frequency, eg using Update=500, instead of the default Update=1000). Then add to the same [Rainmeter] section, an appropriate DefaultUpdateDivider value (in the above example, add DefaultUpdateDivider=2). This way, the meters and measures will be updated on each Update*DefaultUpdateDivider period, so once per second.
Now add an UpdateDivider=1 option to the "incriminated" section. This option will override the default update set with the DefaultUpdateDivider option, having almost the same result as if you'd use subunitary UpdateDivider value on the section.

Oh I was going to add everywhere UpdateDivider=2 except the one I wanted but your solution sounds better and less lame!

[kyriakos876]

Both bangs would be executed.

Great. Thanks again! Really appreciate how fast you answer.

[jsmorley]

Oh I was going to add everywhere UpdateDivider=2 except the one I wanted but your solution sounds better and less lame!

Right, I did point that out in my first answer. It's a question of which is less work for you.

[kyriakos876]

Right, I did point that out in my first answer. It's a question of which is less work for you.

Uh... I misunderstood your first reply and thought you said something else. Now I see it's the same :P

[kyriakos876]

Both bangs would be executed. The entire line is "parsed" and everything is executed in it.

LeftMouseUpAction=[!Log "1"][!DeactivateConfig][!Log "2"]

Even with that, both !Log bangs would happen, even though the skin is unloaded between them.

So, I have

Code: Select all

LeftMouseUpAction=[!ShowMeter SomeMeter][!Refresh][!ShowMeter SomeOtherMeter]

Evetytome a refresh happens it restores every Set bang in the skin but here what's gonn happen if both meters have Hidden=1? Show both meters refresh and then hide them again or show one meter refresh and show the other after the refresh?