I recently noticed one of my skins which used a PingPlugin measure was acting up and spraying thousands of debug lines into the log. I whittled the problem down to the basics below.
Part of the issue is that the skin uses a high update rate due to some animations, but does use a DefaultUpdateDivider to get most everything back to an update time of 1000ms. I had a PingPlugin measure with some conditional logic that required DynamicVariables=1 on the measure. When this happens, the plugin goes bonkers.
The following is the example code from the manual, with some minor changes. The and settings were added/revised, along with the last 2 lines of the . Please note the measure is Disabled!
If this skin is loaded (and Rainmeter is in Debug mode), it will immediately begin spraying messages into the log:
Code: Select all
[Rainmeter] Update=20 DefaultUpdateDivider=50 BackgroundMode=2 SolidColor=0,0,0,255 [MeasurePing] Measure=Plugin Plugin=PingPlugin DestAddress=www.google.com Disabled=1 DynamicVariables=1 [MeterPing] Meter=String MeasureName=MeasurePing X=5 Y=5 W=200 H=20 FontColor=255,255,255,255 Text=google.com: %1ms
So, the point of this posting is to point out that the plugin measure initialization code appears to be running at 20ms intervals (due to ) and doing something repeatedly (name resolution?) despite the measure being disabled, and it is because of DynamicVariables. If you comment out this line, the skin runs normally.
Code: Select all
PingPlugin.dll: Evaluating: www.google.com (Index: 0) (Test\Test.ini - [MeasurePing]) PingPlugin.dll: Found IPv4 address for: www.google.com (Test\Test.ini - [MeasurePing])
I'm not sure whether this is a bug in the plugin, a glitch in my test skin,... OR that the documentation may simply need to say "don't use DynamicVaribles=1 with PingPlugin". Or some combination.