I've made some tweaks, renaming IgnoredProcesses to GlobalIgnoredProcesses and ExtraIgnoredProcesses to SpecificIgnoredProcesses and wired the plugin into the Rainmeter logging framework. So, I bumped it to Version 1.0. It is again uploaded here: http://customize.org/rainmeter/skins/82306 If you upgrade to the new version, be sure to update your .ini files to handle the renaming of this variables.DigitalDJ wrote:I updated TopProcesses again to fix the IgnoredProcess thing Now v0.033.
I've reproduced this issue using Rainmeter-2.1-r848 on a VirtualBox instance of Win 8 x32 home. This plugin in written in C#, so I was also experiencing the issue discussed here: http://code.google.com/p/rainmeter-outlook/issues/detail?id=3 and here http://rainmeter.net/forum/viewtopic.php?f=18&t=7630. I actually think the refresh issue and the multiple-process issue are related since they both do many things similarly. I've added debugging code into my plugin and when Rainmeter is locked in either the refresh case or the two-process case, it doesn't even get to the plugin code.Vorron wrote:I tried to use Rainmeter-2.1-r848 and it crashed. I tried to use it on Windows 7 Ultimate x32 on other partition of my disk and rainmeter crashed. I tried to use it on Windows XP x32 in VirtualBox and it worked properly. Perhaps the problem in my hardware (Samsung R560) or in Windows 7 x32.
But, I have a couple of work-arounds... Since I've only seen these issues on Win 7 x32, you could just use another version of Windows Or, just make a copy the DLL, call it TopProcesses2.dll, and have one measure call TopProcesses.dll and the other TopProcesses2.dll. Be sure that both have ReQuery=1 and use GlobalIgnoredProcesses for anything you want to filter.
This worked for me during my tests. Let me know how it turns out for you.
-ch_rob