HUD question

Hi again folks.

I'm to the point were I need a HUD to control parts of what I am doing.

My question is simple. How on Earth do I get my HUD to know which object I want it to affect?

For instance, let's say I want to use my HUD to rotate a particular prim/object out of several unlinked prims/objects . How would I relay to the HUD exactly which one to rotate? I assume that I would click on the desired object, and then touch whatever button on my HUD to carry out the action. I would further assume that I want the HUD to know what the key is that it needs to take action on. But how do I get the key to the HUD?

I've seen this done in videos of the prim aligning tools. But it evades me atm.

My initial thoughts are to place a script in each object that allows it to Whisper its key to the HUD after being touched. Then the HUD could whisper back, including the key in the message to prevent all the other objects from listening, and "tell" it what to do.

However, I think I am overcomplicating this, so...

A short kick in the right direction should do. Thanks.

http://rpgstats.com/wiki/index.php?title=LlDialog

The key you send in the llDialog call is the av you want to see the dialog box. You also send it a channel number. The prim that sent the box should be listening to this channel number.

I really don't know much about attached huds, so this may be totally off your topic.

hth

ed

Easiest way (?) would be for the prims to have a script which when touched just turns them on to listen (and all others to no longer listen) to a specific channel that the HUD will then broadcast on.

If you broadcast teh owner key as well then you should stop inadvertant mangling of your next door neighbours build.

AFAIK, HUDS listen at the same coordinates as the owner. I gather your HUD tells a prim how to react. so there is already outgoing communication on some channel. One solution would be for the object to tell the HUD (on the same or a related channel) that it's been touched. The object key is then available (from the listen event) to the HUD to save and tag command messages for one prim only.

I agree it's a good idea to include the owner's key in the messages to limit its operation to the same owner's prims.

Okay, thanks. It seems then that I wasn't overcomplicating things after all, as I appear to be on the right track. I'll deffinitely use the owner id as a safeguard though.
Thanks for the help.