User configuration sans-lag

If I want to make an object with some degree of user configurability it seems the only flexible way to do this is with a listerener that parses spoken commands. I've been around long enough to know that unnecessary listeners are frowned upon, so how about this:- You have a touch handler that checks if the agent touching is the owner. If they are the owner it creates a listener and sets a timer for some time like a minute or two. When the timer expires the listener is closed.

Would that be OK?

I've done this before...

It still has problems in laggy areas accepting commands but at least it isn't contributing to the problem. Another way to do it is to listen for a "done" command for when the user is done configuring.

I still prefer notecard configurations but it seems people are either too lazy or against the idea in general (admittedly, it can be a pain to edit the objects contents and then go to the notecard itself, especially considering the relative ease of voice commands.)

Of course, the touch-to-configure method is kind of annoying with attached things.

End of useless commentary

--Jack Lambert

that's a good idea Richard but you could maybe cut out a step if you had the touch start up a dialog thingy with llDialog(). it uses a listener which you could turn on and off like you say but the person would only need to click buttons instead of saying things so it might be less work for them and less spam from the object.

Yes, dialogs my be OK for some of the things that I want to do and it would make it easier for the user as you say, but for some thing you want the user to give a number or a name or whatever.

If you want to try something different, you could require the owner to touch the object for 3 seconds to enter configuration mode. Once entered, the object rezes a temp_on_rez primset resembling a menu. Click a menu choice and the first primset is dies, and rezes a new temp_on_rez menu... for input that isn't a simple check-box, the menu would IM a prompt for the input and enable a privavte channel listen such as; "Type /1 followed by Team 1 Name:"

The temp_on_rez menu displays could then communicate to the parent object by private channel. You could build the entire menu display as one texture, separating the elements as needed.