Difference between revisions of "LlRequestUsername"

From Second Life Wiki
Jump to navigation Jump to search
m (grammar)
m
Line 1: Line 1:
{{#vardefine:p_data_desc|DATA_* flag}}{{LSL_Function
{{LSL_Function
|inject-1
|inject-2={{LSL Function/avatar|id}}
|inject-2={{LSL Function/avatar|id}}
{{Issues/SCR-388}}
|func_id=359|func_sleep=0.0|func_energy=10.0
|func_id=359|func_sleep=0.0|func_energy=10.0
|func=llRequestUsername
|func=llRequestUsername

Revision as of 21:45, 12 August 2012

Summary

Function: key llRequestUsername( key id );

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 the agent username 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>

Important Issues

~ All Issues ~ Search JIRA for related Bugs
   llRequestUsername dataserver event returns "???" while llGetUsername returns correct value

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>

See Also

Events

•  dataserver

Functions

•  llGetUsername

Deep Notes

All Issues

~ Search JIRA for related Issues
   llRequestUsername dataserver event returns "???" while llGetUsername returns correct value

Signature

function key llRequestUsername( key id );