Reply to thread

Message

<blockquote data-quote="hurley" data-source="post: 1167835" data-attributes="member: 151395">Hello Micropolis, my apologies for the slow response, I have been rather swamped of late.My initial thought was for a Tv-Server plugin, but on reflection, since users may want the status indicator LED's on client machines, a service or tray app much like HTPCInfo TVServer Monitor would be ideal.This would require polling however, which is how I originally implemented the feature in a console application.I put the idea out to others because I really can't spare the time to focus on it at least until I've completed some other projects, but I might revisit the idea in a few weeks.Perhaps I could make a stand-alone app or utilise your new shared memory api or even branch your new codebase to include the feature and then send it to you for approval/inclusion in HTPCInfo TVServer Monitor?In regards to the shared memory option, it would be nice if the CardState was delivered as an enumerable integer value rather than/as well as a string value.This would remove the necessity to parse the string values. (May need to be a flags type enum to accommodate bitwise combinations). Just a thought.What does the suffix locked refer to in relation to Card State? Signal lock?I've tested your new version 1.2.6 and it works perfectly here, even in my ancient WinXP MePo 1.3 environment.My only concern is the default update interval is far too slow for semi-real time status monitoring.However it seems to run just as efficiently at 2000 ms or even 1000 ms via the command line switch.regards and happy holidays, hurley</blockquote>

[QUOTE="hurley, post: 1167835, member: 151395"] Hello Micropolis, my apologies for the slow response, I have been rather swamped of late. My initial thought was for a Tv-Server plugin, but on reflection, since users may want the status indicator LED's on client machines, a service or tray app much like HTPCInfo TVServer Monitor would be ideal. This would require polling however, which is how I originally implemented the feature in a console application. I put the idea out to others because I really can't spare the time to focus on it at least until I've completed some other projects, but I might revisit the idea in a few weeks. Perhaps I could make a stand-alone app or utilise your new shared memory api or even branch your new codebase to include the feature and then send it to you for approval/inclusion in HTPCInfo TVServer Monitor? In regards to the shared memory option, it would be nice if the [I]CardState[/I] was delivered as an enumerable integer value rather than/as well as a string value. This would remove the necessity to parse the string values. (May need to be a flags type enum to accommodate bitwise combinations). Just a thought. What does the suffix [I]locked[/I] refer to in relation to Card State? Signal lock? I've tested your new version 1.2.6 and it works perfectly here, even in my ancient WinXP MePo 1.3 environment. My only concern is the default update interval is far too slow for semi-real time status monitoring. However it seems to run just as efficiently at 2000 ms or even 1000 ms via the command line switch. regards and happy holidays, hurley [/QUOTE]

Verification