balala wrote: ↑July 5th, 2019, 6:29 pm
I doubt a code with such a low Update (Update=25 in this case) is using less resources then the code with default update, working with the ActionTimer plugin. I simply doubt this. From my experience, I can say the codes working with ActionTimer measures are most efficient ones.
In this case, if you run these 2 skins alone, the Loop method version uses 0~1% (always less than 1% CPU) while the ActionTimer method skin, set to run continuously, uses 0.5~1.5%.
I will leave it up to the OP to decide what method works best for him based on what else is happening in the skin. The Loop measure skin has a default update of 1000 ms (25X40) and only the 2 measures and image meter are running at the faster update rate.
eclectic-tech wrote: ↑July 5th, 2019, 8:34 pm
The Loop measure skin has a default update of 1000 ms (25X40) and only the 2 measures and image meter are running at the faster update rate.
Theoretically yes, but practically, this is not always true. Yes, I know this was the intention when the DefaultUpdateDivider was introduced, but on a much more complex skin there are a lot of details to be taken into account.
eclectic-tech wrote: ↑July 5th, 2019, 8:34 pm
It's good to have options.
As you extend this into a more realistic use, do be very careful to design it thoughtfully. Ensure things have a chance to "finish" before you restart the actions, and remember that ActionTimer is not "free", abusing it can lead to laggy mouse actions and other unpleasant stuff, even crashing Rainmeter.