SilverAzide / Modernizer

Gadgets Modernizer Patch
23 stars 1 forks source link

Re-add manuafactures logo at cpu meter #1

Closed Siggi0904 closed 2 years ago

Siggi0904 commented 2 years ago

Hi,

can you re add the manufactures brand logo at cpu meter please?

with modernizer: grafik

Before: grafik

Great thanks.

SilverAzide commented 2 years ago

Well, using generic "flat" logos is kind of the point of the whole "modern" look. But luckily you can easily switch this back if you want (I prefer the brand logos too, TBH 😉).

Navigate to your Rainmeter skins folder, and open the Gadgets\@Resources\CpuVariables.inc file with a text editor. Set the following variable, like so:

UseGenericIcons=0

Refresh the skin and you should be good to go!

Siggi0904 commented 2 years ago

Okay, I asked because of the GPU meter gadget has the brand logo from the NVIDIA graphics card. With this point, I thin it was missed at the CPU meter.

Thanks, I'll test your advice.

SilverAzide commented 2 years ago

Yes, you're right.... I really reeeeeeally didn't want to change the GPU Meter icon. So I convinced myself they were "flat enough" and skipped it. 😄 Hopefully no one will mind too much. It's pretty easy to switch this to generic colored icons, if someone wants it.

Siggi0904 commented 2 years ago

Okay, thanks for the info. Then, all is clear.

Another question. I saw, that the time for uptime between logon is quite short. And the logon time differs to the real logon time to my local account. Is there any known bug for these times?

Thanks.

SilverAzide commented 2 years ago

Good question! These two values are coming from two Rainmeter measures: SysInfo (USER_LOGONTIME) and Uptime. They are showing values for me today that are about ~3 minutes apart, which I think is about right. I'm not sure where/how Rainmeter is getting the logon time; I recall when the SysInfo logon time was added that this was a complicated value to obtain. If I recall correctly, I think they are getting this value from the Event log, so it can easily differ from your actual local logon time by some amount. The "net user " command doesn't work for AD accounts, and the AD commands don't work for local accounts, so I think that is why they are using the Event log.

You can probably get better info posting this on the Rainmeter forums; the Chronometer skin is just showing what Rainmeter is reporting, so there's not much I can do if it looks off.

Siggi0904 commented 2 years ago

thanks for the Info. But I have the same 3minutes beteen uptime and logon. We're working at same time schedule. :-D

But Rainmeter wrote in there docs, it is better to use the SysInfo plugin up from windows 10 for the login time. Because of that, can you check the usage of these sysinfo plugin? See: https://docs.rainmeter.net/manual/measures/uptime/

And you commented this topic in the forum too :-) https://forum.rainmeter.net/viewtopic.php?t=27456

Thanks.

Siggi0904 commented 2 years ago

And I don't know if this following topic is up to date, but same problem, I think.

See: https://forum.rainmeter.net/viewtopic.php?t=17680

SilverAzide commented 2 years ago

Gotcha... but I'm not sure I'm following you now. Are you implying that there a problem?

The Digital Clock skin uses the exact code you referenced above in jsmorley's USER_LOGONTIME post. This feature was added to Rainmeter after a long discussion on the Forums between myself and others on how to get this value reliably, and jsmorley came up with a way to add it to Rainmeter natively. The Digital Clock skin was using the QUSER command to get this value prior to it being added to Rainmeter (Gadgets 4.0.0 was the first version to use this new feature, back in 2018).

The caution with hybrid shutdowns is still valid; there is nothing that can be done about that. The docs include ways to do full shutdowns, and you can turn this off completely if you wanted.

Let me know what your concerns are.

Siggi0904 commented 2 years ago

hm, thanks for the explanation.

But actually I think the values are wrong. Uptime is correct, I think. But logon time not.

If I start my pc and wait with login arround 5 minutes the gaget shows only 3 minutes. In these case, this point should be checked and should be corrected, if possible.

If it is not possible, then I'll close these gadget and work without these information's. It's not a problem, but other ueser could ask too.

Great thanks.

SilverAzide commented 2 years ago

Oh, I see... well, I'm not sure I can help you. This would be a question for the Rainmeter devs. The skin is just reporting what Rainmeter says is the logon time.

If you don't want to see the logon tine, you can just turn it off. Click the wrench icon to open the Settings and uncheck the "Show Logon Time" option.

You can try looking at other tools to confirm the data if you like, but in my case it is agreeing almost exactly. Go to Rainmeter > About > Skins and select the Chronometer skin. Scroll down until you see the measure MeasureUserLogonTime. This will show the time Windows says you logged on. You can compare this to the quser command to see if there is a difference, although this isn't quite as exact down to the second. There are other ways to get this as well if you have a domain account (using AD).

logon

If you log off and log back on, you should see the new logon time.

Siggi0904 commented 2 years ago

hm, I'm not 100% familiar with with these datas. I only saw in the forum, that values from the sysinfo plugin are better.

If you can check these topic with rainmeter devs. I'll be happier. Because, I dont know all the backgtound what is needed.

Thanks.

Siggi0904 commented 2 years ago

And these are my actual datas. That's not possible because I had wait around 2-4 minutes to login, I was in an other room after switching on my PC

grafik

SilverAzide commented 2 years ago

OK! Well, I'm not sure what to tell you. As I mentioned earlier, that logon date you see is the SysInfo plugin data. That's the only way in Rainmeter to get that value. It should match the QUSER command output. That's when Windows thinks was the time you logged on, so I'm not sure what more I can say...