Supposing I have ~100 of those meters in a skin. (This means I get a "lag time", until the change of the alpha is displayed, that time increases when I add more meters as redrawing everything is a hard job for the CPU)
In the first case I update only one meter but redraw everything, while in the second, I update everything but change (not exactly redraw I think) only the updated meter.
Which solution would be more CPU friendly? (Is there gonna be any difference to being with?)
kyriakos876 wrote:In the first case I update only one meter but redraw everything, while in the second, I update everything but change (not exactly redraw I think) only the updated meter.
Not exactly. When an !Update bang is applied, a redraw of the whole skin is automatically done. That's why the !Update bang doesn't require the !Redraw bang, as !UpdateMeter (or !UpdateMeterGroup) does. So, even the second code does a redraw.
balala wrote:Not exactly. When an !Update bang is applied, a redraw of the whole skin is automatically done. That's why the !Update bang doesn't require the !Redraw bang, as !UpdateMeter (or !UpdateMeterGroup) does. So, even the second code does a redraw.
I understand that both do a redraw but I find the [!Redraw] alone is heavier than the [!Update] in this case (Could be very easily be wrong). That's why I'm asking.
kyriakos876 wrote:I find the [!Redraw] alone is heavier than the [!Update] in this case (Could be very easily be wrong). That's why I'm asking.
However neither I'm not very sure, I wouldn't think it would be, because, as far as I know, the !Update bang also does a regular redraw. Read the second paragraph of the Meters section below: https://forum.rainmeter.net/viewtopic.php?p=126084#p126084
Probably jsmorley will come with some clarifications (I hope).
balala wrote:However neither I'm not very sure, I wouldn't think it would be, because, as far as I know, the !Update bang also does a regular redraw. Read the second paragraph of the Meters section below: https://forum.rainmeter.net/viewtopic.php?p=126084#p126084
Probably jsmorley will come with some clarifications (I hope).
Yeah, this is a bit weird. I'll hope with your for his reply
There is no reason to think that using [!UpdateMeter SomeMeter][!Redraw] is more resource intensive than [!Update], in fact in almost all cases it would be the opposite.
The analogy for !Update step by step would be:
[!UpdateMeasure *][!UpdateMeter *][!Redraw]
And in fact !Update would do just a bit more than that, although that is most of it.
jsmorley wrote:There is no reason to think that using [!UpdateMeter SomeMeter][!Redraw] is more resource intensive than [!Update], in fact in almost all cases it would be the opposite.
The analogy for !Update step by step would be:
[!UpdateMeasure *][!UpdateMeter *][!Redraw]
And in fact !Update would do just a bit more than that, although that is most of it.
Supposing I have ~100 of those meters in a skin. (This means I get a "lag time", until the change of the alpha is displayed, that time increases when I add more meters as redrawing everything is a hard job for the CPU)
In the first case I update only one meter but redraw everything, while in the second, I update everything but change (not exactly redraw I think) only the updated meter.
Which solution would be more CPU friendly? (Is there gonna be any difference to being with?)