Another terrible idea, along the lines of:This seems to work. However, I'm not entirely sure for how long, if by any chance the stack is building up internally - only use it if you know what you're doing.
P.S. I "only" have 12 logical cores, thus the upper limit in the above code. It can obviously be adjusted for a larger number of cores.
which doesn't require a low update, just a VERY careful self update of the sole UsageMonitor measure to avoid endless loops:Well, now that you said it, while such a possibility exists via self updating the measure dynamically with every core index from 1 to 24, you're right that it's not a feasible one since you have no guarantees that the retrieved values will be for the same second of measurement, or that it will even work in the context of UsageMonitor.
Code:
[Variables]Core=0PUCore0=0PUCore1=0PUCore2=0PUCore3=0PUCore4=0PUCore5=0PUCore6=0PUCore7=0PUCore8=0PUCore9=0PUCore10=0PUCore11=0[Rainmeter]Update=1000AccurateText=1DynamicWindowSize=1[MeasurePU]Measure=PluginPlugin=UsageMonitorCategory=Processor InformationCounter=% Processor UtilityName=0,#Core#IfCondition=(#Core#<12)IfTrueAction=[!SetVariable PUCore#Core# [#CURRENTSECTION#:]][!SetVariable Core (#Core#+1)][!UpdateMeasure #CURRENTSECTION#]IfFalseAction=[!SetVariable Core 0][!UpdateMeter Result][!Redraw]IfConditionMode=1DynamicVariables=1[Result]Meter=StringPadding=140,5,130,5FontColor=0,0,0,255SolidColor=150,150,150,255FontSize=10AntiAlias=1Text=Core 0: #PUCore0# %#CRLF#Core 1: #PUCore1# %#CRLF#Core 2: #PUCore2# %#CRLF#Core 3: #PUCore3# %#CRLF#Core 4: #PUCore4# %#CRLF#Core 5: #PUCore5# %#CRLF#Core 6: #PUCore6# %#CRLF#Core 7: #PUCore7# %#CRLF#Core 8: #PUCore8# %#CRLF#Core 9: #PUCore9# %#CRLF#Core 10: #PUCore10# %#CRLF#Core 11: #PUCore11# %UpdateDivider=-1DynamicVariables=1P.S. I "only" have 12 logical cores, thus the upper limit in the above code. It can obviously be adjusted for a larger number of cores.
Statistics: Posted by Yincognito — Today, 1:14 am