Difference between revisions of "LlRequestUsername"
Jump to navigation
Jump to search
All Issues ~ Search JIRA for related Bugs
(globals gone wild) |
|||
Line 10: | Line 10: | ||
|return_text=that is used to identify the [[dataserver]] event when it is raised. | |return_text=that is used to identify the [[dataserver]] event when it is raised. | ||
|spec | |spec | ||
|caveats=*If you merely wish to show avatar name information in the viewer window, it may be more straightforward to avoid a dataserver event | |caveats= | ||
*If you merely wish to show avatar name information in the viewer window, it may be more straightforward to use [[Viewer URI Name Space]] and avoid a dataserver event, e.g.:<lsl>llSay(0, "secondlife:///app/agent/" + (string)id + "/username");</lsl> | |||
|constants | |constants | ||
|examples=<lsl>key owner_name_query; | |examples=<lsl>key owner_name_query; |
Revision as of 16:45, 24 February 2012
LSL Portal | Functions | Events | Types | Operators | Constants | Flow Control | Script Library | Categorized Library | Tutorials |
Summary
Function: key llRequestUsername( key id );359 | Function ID |
0.0 | Forced Delay |
10.0 | Energy |
Requests the Username of the agent identified by id. When Username is available the dataserver event will be raised. The agent identified by id does not need to be in the same region or online at the time of the request.
Returns a key that is used to identify the dataserver event when it is raised.
• key | id | – | avatar UUID |
Caveats
- If you merely wish to show avatar name information in the viewer window, it may be more straightforward to use Viewer URI Name Space and avoid a dataserver event, e.g.:<lsl>llSay(0, "secondlife:///app/agent/" + (string)id + "/username");</lsl>
Examples
<lsl>key owner_name_query;
default {
state_entry() { owner_name_query = llRequestUsername(llGetOwner()); }
dataserver(key queryid, string data) { if ( owner_name_query == queryid ) { llSay(0, "The username of the owner of this script : " + data); } }}</lsl>