Re: Rules for Instance WAS PIC testing WAS OSD ALERT

[Frank Mc Alinden]

>E.g. if you used hardcoded like 12345, 12346, 12347 the >xplhal
manager user
>would send it a more user friendly name like KITCHEN and >it would
use this.

>On reboot it would go back to 12345 (or whatever) but >xplhal would
>automatically put it back to KITCHEN ready for use

Oh i see then it only needs to be saved in Ram......So my OSD could have
aec-tvosd.tv1 hardcoded and the user programs a friendly name ...I like
this as
the ram would be quicker to access.....when parscing the message......Ok to
do
this ???

Tony will your dev com display the hbeat message my pic sends ??
Thanks
Frank
----- Original Message -----
From: Tony Tofts
To: <a
href="/group/ukha_xpl/post?postID=YXyjGso_rIMmXKXM57460-JKC6MjdA8yHh5qPUfAAGRTXq1GQ7jy4Bk2a5VNwVOOBpwOHZw7Bi4Bkl5J81s-dpw">ukha_xpl@xxxxxxx</a>
Sent: Wednesday, December 10, 2003 8:38 PM
Subject: RE: [ukha_xpl] Rules for Instance WAS PIC testing WAS OSD ALERT


> >Hardcoded to a single instance (only 1 per network)
>
> Doesnt Ian want this to be configurable ??

Preferably it would be able to store a temporary change

E.g. if you used hardcoded like 12345, 12346, 12347 the xplhal manager user
would send it a more user friendly name like KITCHEN and it would use this.

On reboot it would go back to 12345 (or whatever) but xplhal would
automatically put it back to KITCHEN ready for use

Regards
Tony