AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Tools better than imagealpha12/4/2023 ![]() ![]() My focus would be on making sure that as much as possible, measures are updated only and exactly when they need to be. However, I suspect it is the work that measures do (and possibly redrawing a complicated skin with a low update rate) that use the most resources. Not saying that fine-tuning isn't a good thing, and saving a CPU cycle is saving a CPU cycle. Moving bits from one bucket to another inside a program and doing addition and subtraction are what computers do with the least amount of effort. What you save with UpdateDivider=-1 on a meter is having the meter retrieve the current value of any measures or variables used in it and resolve formulas in options, which at the end of the day is probably the least resource intensive work Rainmeter does. This has not been true for some time, images are now "cached" and there is no real savings from "freezing" a static image meter anymore. UpdateDivider=-1 used to make a huge difference with image meters, as the image was retrieved from disk on each update. This is why you generally, if not always, follow !UpdateMeter with !Redraw, and why there isn't a !RedrawMeter. ![]() The entire skin is always redrawn on every update. There are no actual "layers" in a Rainmeter window, and in reality the entire thing is one plane drawn in order on the single window. It is all or nothing as far as redrawing the skin goes. Great tips, but in my view is it possible to go to great lengths and not really save any appreciable resources.Īs far as updating meters, remember that setting a meter to UpdateDivider=-1 doesn't keep Rainmeter from redrawing the meter, if ANY single pixel anywhere else in the skin is redrawn.
0 Comments
Read More
Leave a Reply. |