by Dean Roddey » Sat Oct 30, 2004 5:49 am
I just wanted to come back to this, in terms of a general question. How do you deal with such a beast with the UIRT? It seems to send one message first I guess, and then keeps sending another one as long as you are holding the button down. So you can't really deal with it as a repeat count, but in a networked automation system like CQC, just setting the UIRT to blast indefinitely until some user action stops it seems kind of dangerous since the connection can always get lost between starting something and coming back to stop it. I guess you could just set a very large repeat count and let it go and then come back and interrupt it when they release the button (whereever that might be in a system like CQC.)
But in general, what's the blessed way to deal with this kind of thing with the UIRT?