Possible llTemporary( key agentID ); ?

Basicly, I would like to see a function that causes certain property changes to be sent to only ONE agent. This is more of a privacy issue than anything...


Essentially

llSetPrimitiveParams( [PRIM_TEXTURE, -1, Mytexture, ...] );
llTemporary( llGetOwnerKey(llGetKey) );
llSetPrimitiveParams( [PRIM_TEXTURE, -1, SecretTexture, ... );
llTemporary( NULL_KEY);

Basicly, if llTemporary is set, it would define a 'decaling' mode for one agent, and any committed changes would only be sent to that person, and lost if the object should go out of the cache. I don't know of a better way of doing this, but I hate how if you make an object, everyone with some knowledge of camera work can get around walls.

Oh yes, oh god yes.

This would be great, it would allow tartarus to create a GUI like interface by using prims

This would be quite interesting!
I suggest a different name for it though:
llSetUpdateTarget(key agent)

Perhaps even:
llSetUpdateFilter(key agent, integer accept);

That way, we can either choose to have 1 agent not recieve the updates from the object (FALSE), or *only* 1 agent recieving the updates from the object (TRUE).

Although, I'd still want the more simple method, if the more complex method is significantly more difficult to implement.
==Chris

You could just use llGiveInventory, the textures will pop up as a preview window.
Hey Cory:
WE REALLY NEED A BETTER UI TOOLKIT THAN THAT GOD FORSAKEN LLDIALOG!!!
Thank you.
That said, it would be nice to pop up an image with llDialog, have at the very least 6 buttons and a dedicated input field would be handy as well, even if it's just a replica of the chatbox, and uses the current listener system.
Of course what I really want is the ability to make my own windows with radio buttons and checkboxes, drop down menus, etc.
Perhaps getting all the data from a field name - value pair list afterwards.
But hey, if we could get ANY kind of progress in this department, no matter how incremental, it would be most welcome.
You can't seriously expect us to build advanced UIs with prims. It's a pain, and it's location specific. What do you want me to do, add a following script to my GUI ?

There were some threads in the past discussing the ability to make textures that only select people could see. This would seem to be a wider version of that... But I feel in my gut that this particular implementation would not be a safe change to the code -- Nor an easy one.

I just keep thinking, "sniper riffle Scope"