Difference between revisions of "LlGetObjectName"
Jump to navigation
Jump to search
All Issues ~ Search JIRA for related Bugs
m |
Adicted Waco (talk | contribs) m |
||
Line 7: | Line 7: | ||
|return_text=that is the name of the prim the script is attached to. | |return_text=that is the name of the prim the script is attached to. | ||
|spec | |spec | ||
|caveats=*The prim name is limited to | |caveats=*The prim name is limited to 63 bytes, any string longer than that will be truncated. This truncation does not always happen when the attribute is set or read. | ||
|constants | |constants | ||
|examples=<lsl>default | |examples=<lsl>default |
Revision as of 13:33, 23 October 2008
LSL Portal | Functions | Events | Types | Operators | Constants | Flow Control | Script Library | Categorized Library | Tutorials |
Summary
Function: string llGetObjectName( );202 | Function ID |
0.0 | Forced Delay |
10.0 | Energy |
Returns a string that is the name of the prim the script is attached to.
Caveats
- The prim name is limited to 63 bytes, any string longer than that will be truncated. This truncation does not always happen when the attribute is set or read.
Examples
<lsl>default {
state_entry() { llSay(PUBLIC_CHANNEL, llGetObjectName() ); }}</lsl>
Notes
- This function may return "(Waiting)" sometimes.
Presumably the function queries the asset server for a predetermined time and returns "(Waiting)" if that elapses. It then silently proceeds to the next instruction. A work around therefore, might be to test object name is not "(Waiting)" after calling llGetObjectName.
See Also
Functions
• | llSetObjectName | – | Set the prims name | |
• | llGetLinkName | – | Get a linked prims name | |
• | llGetObjectDesc | – | Get the prims description | |
• | llSetObjectDesc | – | Sets the prims description | |
• | llGetObjectDetails |
Articles
• | Prim Attribute Overloading |