Warning Message about Status Property

hec1152 · #1 November 24th, 2009, 12:02 PM

I'm getting the following (warnings) when DooCPU Monitor starts up. I have the "Disable Obsolete API procedure warning messages" set to YES, so I don't know why they are appearing if they are only warnings.

11/24/2009 9:40:02 AM ~!~DooCPU Monitor Info~!~Register callback completed
11/24/2009 9:40:02 AM ~!~Plug-In~!~Initializing Plug-in: DooCPU Monitor
11/24/2009 9:40:02 AM ~!~Warning~!~'status' property on device DooCPU Monitor System CPU Usage was accessed - this property has been deprecated and should not be used.
11/24/2009 9:40:02 AM ~!~Warning~!~'status' property on device DooCPU Monitor System Available Memory was accessed - this property has been deprecated and should not be used.
11/24/2009 9:40:02 AM ~!~Warning~!~'status' property on device DooCPU Monitor HomeSeer CPU Usage was accessed - this property has been deprecated and should not be used.
11/24/2009 9:40:02 AM ~!~Warning~!~'status' property on device DooCPU Monitor HomeSeer Memory Usage was accessed - this property has been deprecated and should not be used.
11/24/2009 9:40:02 AM ~!~Warning~!~'status' property on device DooCPU Monitor HomeSeer Thread Count was accessed - this property has been deprecated and should not be used.
11/24/2009 9:40:10 AM ~!~Plug-In~!~Finished initializing plug-in DooCPU Monitor

Thanks in advance for any advice.

Rupp · #2 November 24th, 2009, 12:04 PM

This is simply a warning and can be ignored until Jim gets time to make the change to the plugin.

hec1152 · #3 November 24th, 2009, 12:15 PM

Ok. I appreciate the quick response.

Jim Doolittle · #4 November 30th, 2009, 11:15 AM

I will provide a fix by the end of the week.

hec1152 · #5 November 30th, 2009, 08:12 PM

There's no hurrry. I now know to ignor these messages as they are benign. Not worth wasting any of your time on it. Thanks for the response.

Jim Doolittle · #6 November 30th, 2009, 09:14 PM

I need to fix it per HST's request anyway. I can see where they want to move forward. I actually had a heads up a few weeks back and corrected the problem in the source code. Even though I have simplified the publishing of a new build, the publishing part tends to be more tedious than changing the code.