First of all, thank you for your answer.
I am reassured that it was not understood as "I expect answers/solutions on a silver platter".
Yes, I think I didn't formulate my question about the MIN value problem very clearly. But that's because I don't know what I actually need to ask.
Because as I can see from your answer, my CPU meter seems to be working as it should. So an error on my part in the code seems to be as good as ruled out.
So it can only possibly be Windows 11, which I am using, and you are still using Windows 10, as far as I understood correctly. Or we have the phenomenon here that for some inexplicable reason, which sometimes happens in IT, one thing does not work or harmonize together. I once saw a report on this. 2 absolutely identical PCs, identical software and drivers, even the screens and peripherals such as mouse, keyboard etc. were all identical. And yet a program wouldn't start on one PC and caused blue screens.
Maybe this MIN value problem is something similar... just inexplicable
Yes, I had understood that the Win11 problems mainly relate to the utilization of individual cores, despite all the circumstances mentioned for me to muddle through here.
It became complicated for me at the point when I read how to calculate/read out what this, that and the other means now, and that of course values such as CPU speed and so on are also influenced by this, and you have to rewrite your meters if you want to have it differently again.
In short, I reached a point yesterday where my head was spinning so much that (don't laugh now) I was about to sell my PC, get an old laptop or tablet for the most necessary office work, and get a games console instead.
And then just forgot how complicated some things in IT have become. Honestly, I had (and still have) lost the motivation to continue working on system metrics such as CPU, GPU, RAM etc. as a result.
Because at the moment I still don't know which value is actually the one I can believe and really matches what the CPU is doing.
The whole thing was topped off by a YT video I watched last night. I actually wanted to switch off from Rainmeter, HWiNFO and co. ... then I saw in the said video that today there is not only the TDP value of a CPU, but also a PPT (Package Power Target) value. And in my mind's eye I saw my CPU meter, which only reads out the TDP value (CDW last bar) and was thinking about whether I should now make a PPT BAR shape.
I really had to mentally slap myself in the face at that moment. I haven't even finished my CPU meter yet, and there may still be errors in it and I don't even know how to get the values read out under the current situation (Win11 problem), so my thoughts are already turning to expanding the CPU -meters.
Oh, so much texting again... Sorry
Back to the topic/core problem.
As I said, I usually state or describe my problems precisely enough.
But when it comes to the MIN-Value problem, which as I said seems to have been written correctly by me in the code, I'm really at a loss. As you can see, it works. Just not on my system.
Therefore, I think neither you nor anyone else has to go through my code line by line, which would be unreasonable penal work given ~1917 lines spread across two files.
The problem is either in Win11, or my PC has a problem somewhere. I can also exclude HWiNFO as a value provider, since the USAGE values come from the “UsageMonitor” plug-in and are then processed accordingly using other measures.
As for third-party programs, you're right. IF, and the emphasis here is on IF, the values they provide are also correct, then even I, as an opponent of third-party programs, will soften here and use them after all.
But that's exactly what's making me ponder at the moment. I use HWiNFO and Co. to combat my inner bastard, only to realize that...
a) these programs sometimes read out so many values that I actually don't even know what is what anymore.
b) When I look for help here in the forum or on the Internet, what I find confuses me even more, and...
c) then also read that the values that come out of it are probably cheese at the moment, because the program manufacturers also have the same problem as the Rainmeter user these days.
And so my autistic streak comes out (once again), wondering what the point of it all is, and could scream and bite the keyboard.
Well, anyway, I think we can consider my not so clearly formulated question about the MIN value to be settled at this point. Because my code seems correct. And since none of you or I can clairvoyance, I'll probably have to live with it for the time being, as this problem seems to be limited to my PC and the problem/error can only be solved on this one.
Of course, I am always open to anything else relating to my CPU meter, such as criticism, ideas or suggestions.
I will continue to use this thread here for my current CPU meter in the future if there are updates etc.