ailia wrote:Chatted up jsmorley a bit, going to add the filtering after all, but with a threshold to show processes that are filtered if CPU crosses the threshold.
Also, what OSes can you test? Sounding like Win 8/8.1 and Win10 need coverage most.
Ah... you went to the SOURCE!
I can test on Win7 32bit, and XP if needed...
Love Rainmeter, but don't need the latest and greatest performance anymore!
ailia wrote:Chatted up jsmorley a bit, going to add the filtering after all, but with a threshold to show processes that are filtered if CPU crosses the threshold.
Also, what OSes can you test? Sounding like Win 8/8.1 and Win10 need coverage most.
Can't say this first round will be user-friendly, but at least it shouldn't crash. Unfortunately no skin is included due to time constraints, but it should be pretty easy to figure out, meter list below should work.
All options funtioning , but I did notice a slight difference in values reported.
Memory usage is slightly lower in the skin, than what is reported in Windows Task Mngr and/or PSList. About 1.5M lower at 50M meg usage; .5M lower at 10M usage.
Here's a screenshot of my test skin & PSList showing WS. Both updating at 1 second intervals
ws.png
Here's a screenshot of my test skin & PSList showing PrivMem. Same update rate
pm.png
Here's a screenshot of my test skin & PSList showing PageSysMem (This is almost exact.).
pgsm.png
You do not have the required permissions to view the files attached to this post.
Release notes: Cpu usage only monitors user programs unless Rainmeter is forced to run under an administrative account. Memory usage has no such restriction.
Next build should support filtering, just didn't get around to it today.
AutoScale=1k should scale at 1024, with kilobyte as the lowest value, but it returns a lower value.
AutoScale=2k returns a higher value, due to the use of 1000 divisor, instead of 1024.
Using any AutoScale value, never returns the correct value?... what am I missing?
EDIT: I did notice this a few weeks ago, when working with the WS mem and PerfMon plugin... it seems to only effect the WS mem values?