Difference between revisions of "Template:LSL Function/prim-desc"

From Second Life Wiki
Jump to: navigation, search
m (I'm sure there is a good reason I created this template.)
m (Fixed some sentences. Fixed a "with by" typo.)
 
Line 4: Line 4:
  
 
{{#vardefine:caveats|{{#var:caveats}}
 
{{#vardefine:caveats|{{#var:caveats}}
*The prim description is [[limit]]ed to 127 [[bytes]], any string longer then that will be truncated. This truncation does not always happen when the attribute is set or read.
+
*The prim description is [[limit]]ed to 127 [[bytes]]; any string longer then that will be truncated. This truncation does not always happen when the attribute is set or read.
*The pipe character '|' and the newline character '\n' are not legal in a prim's description, they will be replaced by with '?'{{Footnote|The pipe character historically has been used to separate fields in the serialized version of inventory. The field is not multi-line so the newline character holds no meaning in this context.}}.
+
*The pipe character '|' and the newline character '\n' are not legal in a prim's description. They will be replaced with '?'.{{Footnote|The pipe character historically has been used to separate fields in the serialized version of inventory. The field is not multi-line so the newline character holds no meaning in this context.}}
*Note that when people have "Hover Tips on All Objects" selected in the viewer's "View" menu, they'll see the object description pop-up for any object under their mouse pointer.  For that reason, it is good practice to only set human-friendly information in the description (e.g. keys and such).
+
*Note that when people have "Hover Tips on All Objects" selected in the viewer's "View" menu, they'll see the object description pop-up for any object under their mouse pointer.  For that reason, it is good practice to only set human-friendly information in the description, e.g. keys and such.
 
*When an attached object is detached, changes made by script to the name and description (of the root prim) of the attachment will be lost. While the object is attached the name and description can be changed but it will not be reflected in inventory. This caveat does ''not'' apply to child prims.
 
*When an attached object is detached, changes made by script to the name and description (of the root prim) of the attachment will be lost. While the object is attached the name and description can be changed but it will not be reflected in inventory. This caveat does ''not'' apply to child prims.
 
}}
 
}}

Latest revision as of 19:15, 22 December 2015

#var value
also_articles
•  Limits SL limits and constrictions
caveats
  • The prim description is limited to 127 bytes; any string longer then that will be truncated. This truncation does not always happen when the attribute is set or read.
  • The pipe character '|' and the newline character '\n' are not legal in a prim's description. They will be replaced with '?'.[1]
  • Note that when people have "Hover Tips on All Objects" selected in the viewer's "View" menu, they'll see the object description pop-up for any object under their mouse pointer. For that reason, it is good practice to only set human-friendly information in the description, e.g. keys and such.
  • When an attached object is detached, changes made by script to the name and description (of the root prim) of the attachment will be lost. While the object is attached the name and description can be changed but it will not be reflected in inventory. This caveat does not apply to child prims.
  1. ^ The pipe character historically has been used to separate fields in the serialized version of inventory. The field is not multi-line so the newline character holds no meaning in this context.