It is just a starting point, I'll look around on the forum and the manual to get better with the coding .
Regards
Definitely neat to have Rainmeter on a dedicated external screen. One possible improvement: the the default Update=1000 in the [Rainmeter] section (1 update/second), is a relatively 'safe' default value for most modern PCs, and for a small config like you're using here, you could probably instead set it to Update=500 (2 updates/second) easily or even Update=250 (4 updates/second) and have a better visual 'framerate'.
Normally it's not worth it to have a fast update rate draining resources unnecessarily; here I think a bit faster update rate is worth it since the screen will always be seen (and should still be low impact at 500 or 250).
You can add something like below to monitor the CPU usage of Rainmeter and experiment with values:
Alex88 wrote: ↑February 14th, 2021, 1:29 am
Definitely neat to have Rainmeter on a dedicated external screen. One possible improvement: the the default Update=1000 in the [Rainmeter] section (1 update/second), is a relatively 'safe' default value for most modern PCs, and for a small config like you're using here, you could probably instead set it to Update=500 (2 updates/second) easily or even Update=250 (4 updates/second) and have a better visual 'framerate'.
Normally it's not worth it to have a fast update rate draining resources unnecessarily; here I think a bit faster update rate is worth it since the screen will always be seen (and should still be low impact at 500 or 250).
You can add something like below to monitor the CPU usage of Rainmeter and experiment with values:
Thanks for the input I will test this code out, i did try to increase the update rate but it looked a bit strange so I rolled it back to 1000.
For sure I'll try it, I thought about a faster update for the actual line, and let rainmeter draw a second darker ghost one a bit slower to give the effect of a fading trail when it moves, I programmed in the past but I have to get the hang with rainmeter code and see what it can or can't do.
I'm doing some test with the AverageSize command, and it looks like it is doing a great job without the need for the second "ghost" bar, I'll keep testing out right now i'm trying an
Update=20
DefaultDivider=5
And for the CPU and RAM round bars
AverageSize=7
The rest is slower, it looks a lot better and the CPU usage is not that worse max 0.5% difference.
I have also tried to test a super low Update without AverageSize, but outside not looking really that good, it does up a lot the CPU usage.