Difference between revisions of "LlSetText"

From Second Life Wiki
Jump to navigation Jump to search
m (this page needs some more work)
Line 9: Line 9:
|p2_type=vector|p2_name=color
|p2_type=vector|p2_name=color
|p3_type=float|p3_name=alpha
|p3_type=float|p3_name=alpha
|func_desc=Displays {{LSLP|text}} that hovers over the prim with specific {{LSLP|color}} and translucency (specified with {{LSLP|alpha}}).  
|func_desc=Displays {{LSLP|text}} that hovers over the prim with specific {{LSLP|color}} and translucency (specified with {{LSLP|alpha}}).
|return_text
|return_text
|spec=
|spec=
Line 16: Line 16:
*{{LSLP|text}} is [[limit]]ed to 254 [[bytes]], if the string is longer it will be truncated to 254 bytes, even if that means the truncation will chop a character in half.
*{{LSLP|text}} is [[limit]]ed to 254 [[bytes]], if the string is longer it will be truncated to 254 bytes, even if that means the truncation will chop a character in half.
*An unbroken line of text of a great length may be broken automatically into two lines (one above the other).
*An unbroken line of text of a great length may be broken automatically into two lines (one above the other).
*Floating text can be seen through walls and other object. Be considerate of neighbors in malls and apartment buildings.  
*Floating text can be seen through walls and other object. Be considerate of neighbors in malls and apartment buildings.
**Visibility distance increases with prim size.
**Visibility distance increases with prim size.
*Removing the script or deactivating it will not remove the prim's floating text.
*Removing the script or deactivating it will not remove the prim's floating text.
Line 22: Line 22:
*To remove floating text, use the following:
*To remove floating text, use the following:
<lsl>
<lsl>
//  ZERO_VECTOR has the vector value <0.0, 0.0, 0.0>
//  black & transparent
//  when used as a color it's black
 
     llSetText("", ZERO_VECTOR, 0.0);
     llSetText("", ZERO_VECTOR, 0.0);
</lsl>
</lsl>
*Shift-copying does not keep the floating text prim property. If the llSetText() script is not triggered when a copy made, the copy will not have the floating text.
*Shift-copying does not keep the floating text prim property. If the [[llSetText]]() script is not triggered when a copy made, the copy will not have the floating text.
*Vertical whitespace is removed from the end of the text string, so if you want vertical whitespace put any character (like a space) on the last line.
*Vertical whitespace is removed from the end of the text string, so if you want vertical whitespace put any character (like a space) on the last line.
*Multiple linebreaks with empty lines are converted to a single linebreak, so add a whitespace character on every line you want to skip:
*Multiple linebreaks with empty lines are converted to a single linebreak, so add a whitespace character on every line you want to skip:
<lsl>
<lsl>
    vector COLOR_WHITE = <1.0, 1.0, 1.0>;
    float  OPAQUE      = 1.0;
//  Bad:
//  Bad:
     llSetText("Monkeys\n\n\n\n\n", <1.0, 1.0, 1.0>, 1.0);
     llSetText("Monkeys\n\n\n\n\n", COLOR_WHITE, OPAQUE);


//  Good:
//  Good:
     llSetText("Monkeys\n \n \n \n \n ", <1.0, 1.0, 1.0>, 1.0);
     llSetText("Monkeys\n \n \n \n \n ", COLOR_WHITE, OPAQUE);
</lsl>
</lsl>
*Measurements showed a high impact of process time when doing numerous iterations in a while loop. For approx. 65K iterations the process times are ca. 5s without float text, 24s with llSetText and 96s when using llSetLinkPrimitiveParamsFast/PRIM_TEXT. Thats why its not adviced to make excessive use of a float text within such iterations.
*Measurements showed a high impact of process time when doing numerous iterations in a while loop. For approx. 65K iterations the process times are ca. 5s without float text, 24s with llSetText and 96s when using [[llSetLinkPrimitiveParamsFast]] in combination with [[PRIM_TEXT]]. Thats why its not adviced to make excessive use of a float text within such iterations.
|examples=
|examples=
Example of how llSetText could be included in default code to show prim's name in green text:
Example of how [[llSetText]] could be included in default code to show prim's name in green text:
<lsl>
<lsl>
default
default
Line 45: Line 46:
     state_entry()
     state_entry()
     {
     {
         llSay(0, "Hello, Avatar!");
         llSay(PUBLIC_CHANNEL, "Hello, Avatar!");


     //  prim's name (not necessarily object's) in green and opaque
     //  prim's name (not necessarily object's) in green and opaque
Line 53: Line 54:
     touch_start(integer total_number)
     touch_start(integer total_number)
     {
     {
         llSay(0, "Touched.");
         llSay(PUBLIC_CHANNEL, "Touched.");
     }
     }
}
}
Line 64: Line 65:
! Code
! Code
{{!}}- style="background:white"
{{!}}- style="background:white"
{{!}}White  
{{!}}White
{{!}}<1.0, 1.0, 1.0>
{{!}}<1.0, 1.0, 1.0>
{{!}}- style="background:grey"
{{!}}- style="background:grey"
{{!}}Grey  
{{!}}Grey
{{!}}<0.5, 0.5, 0.5>
{{!}}<0.5, 0.5, 0.5>
{{!}}- style="background:black; color:white;"
{{!}}- style="background:black; color:white;"
{{!}}{{!}}Black  
{{!}}{{!}}Black
{{!}}<0.0, 0.0, 0.0>
{{!}}<0.0, 0.0, 0.0>
{{!}}- style="background:red; color:white;"
{{!}}- style="background:red; color:white;"
Line 84: Line 85:
The x, y & z components of the vector are used to represent red, green, and blue respectively. The range is different than traditional RGB, instead of being 0 -> 255, LSL uses 0 -> 1. <1.0, 1.0, 1.0>, means "white" and <0.0, 0.0, 0.0> means "black":
The x, y & z components of the vector are used to represent red, green, and blue respectively. The range is different than traditional RGB, instead of being 0 -> 255, LSL uses 0 -> 1. <1.0, 1.0, 1.0>, means "white" and <0.0, 0.0, 0.0> means "black":
<lsl>
<lsl>
//  <1.0, 1.0, 1.0> as color is white
//  white & opaque
 
     llSetText("I am white", <1.0, 1.0, 1.0>, 1.0);
     llSetText("I am white", <1.0, 1.0, 1.0>, 1.0);
</lsl>
</lsl>
<lsl>
<lsl>
//  ZERO_VECTOR is <0.0, 0.0, 0.0> and as color black
//  black & opaque
 
     llSetText("I am black", ZERO_VECTOR, 1.0);
     llSetText("I am black", ZERO_VECTOR, 1.0);
</lsl>
</lsl>
The 1.0 is the alpha setting. 1.0 means fully opaque, and 0.0 would be completely transparent (invisible):
The 1.0 is the alpha setting. 1.0 means fully opaque (alpha), and 0.0 would be completely transparent (invisible):
<lsl>
<lsl>
     llSetText("green text with alpha 0.5", <0.0, 1.0, 0.0>, 0.5);
     llSetText("green text with alpha 0.5", <0.0, 1.0, 0.0>, 0.5);
Line 107: Line 106:
//  two lines of green text
//  two lines of green text


     llSetText("I am \n on two lines!", <0.0, 1.0, 0.0>, 1.0);
     llSetText("I am\non two lines!", <0.0, 1.0, 0.0>, 1.0);
</lsl>
</lsl>
|helpers=
|helpers=
Line 118: Line 117:
     state_entry()
     state_entry()
     {
     {
    //  black and transparent
         llSetText("", ZERO_VECTOR, 0.0);     // after removing the float text of the prim
         llSetText("", ZERO_VECTOR, 0.0);
         llRemoveInventory(llGetScriptName());// we remove the script, too
 
         llRemoveInventory(llGetScriptName());
     }
     }
}
}

Revision as of 10:35, 8 October 2013

Summary

Function: llSetText( string text, vector color, float alpha );
0.0 Forced Delay
10.0 Energy

Displays text that hovers over the prim with specific color and translucency (specified with alpha).

• string text floating text to display
• vector color color in RGB <R, G, B> (<0.0, 0.0, 0.0> = black, <1.0, 1.0, 1.0> = white)
• float alpha from 0.0 (clear) to 1.0 (solid) (0.0 <= alpha <= 1.0)

Caveats

  • Do not rely on Floating Text as a storage medium; it is neither secure nor finalized.
    • Floating text has been altered in past server updates, breaking existing content; future changes may occur.
    • Even "invisible"[1] floating text is transmitted to the client.
      • It can be viewed by anyone with a client that is capable of rendering text that is supposed to be invisible.
      • The network packets that contain the text can be sniffed and the text read.
  • If more than one llSetText is called (By reset,interaction or script state) within a prim the latest call will take priority over the previous.
  • text is limited to 254 bytes, if the string is longer it will be truncated to 254 bytes, even if that means the truncation will chop a character in half.
  • An unbroken line of text of a great length may be broken automatically into two lines (one above the other).
  • Floating text can be seen through walls and other object. Be considerate of neighbors in malls and apartment buildings.
    • Visibility distance increases with prim size.
  • Removing the script or deactivating it will not remove the prim's floating text.
    • Floating text is a prim property and not dependent on a script for its continued existence.
  • To remove floating text, use the following:

<lsl> // black & transparent

   llSetText("", ZERO_VECTOR, 0.0);

</lsl>

  • Shift-copying does not keep the floating text prim property. If the llSetText() script is not triggered when a copy made, the copy will not have the floating text.
  • Vertical whitespace is removed from the end of the text string, so if you want vertical whitespace put any character (like a space) on the last line.
  • Multiple linebreaks with empty lines are converted to a single linebreak, so add a whitespace character on every line you want to skip:

<lsl>

   vector COLOR_WHITE = <1.0, 1.0, 1.0>;
   float  OPAQUE      = 1.0;

// Bad:

   llSetText("Monkeys\n\n\n\n\n", COLOR_WHITE, OPAQUE);

// Good:

   llSetText("Monkeys\n \n \n \n \n ", COLOR_WHITE, OPAQUE);

</lsl>

  • Measurements showed a high impact of process time when doing numerous iterations in a while loop. For approx. 65K iterations the process times are ca. 5s without float text, 24s with llSetText and 96s when using llSetLinkPrimitiveParamsFast in combination with PRIM_TEXT. Thats why its not adviced to make excessive use of a float text within such iterations.

Examples

Example of how llSetText could be included in default code to show prim's name in green text: <lsl> default {

   state_entry()
   {
       llSay(PUBLIC_CHANNEL, "Hello, Avatar!");
   //  prim's name (not necessarily object's) in green and opaque
       llSetText(llGetObjectName(), <0.0, 1.0, 0.0>, 1.0 );
   }
   touch_start(integer total_number)
   {
       llSay(PUBLIC_CHANNEL, "Touched.");
   }

} </lsl> By default the floating text will appear on a single line. However, the floating text can be spread over multiple lines by using a line break "\n" (read SplitLine in section 'See Also').

Color & Alpha

Color Code
White <1.0, 1.0, 1.0>
Grey <0.5, 0.5, 0.5>
Black <0.0, 0.0, 0.0>
Red <1.0, 0.0, 0.0>
Green <0.0, 1.0, 0.0>
Blue <0.0, 0.0, 1.0>

The x, y & z components of the vector are used to represent red, green, and blue respectively. The range is different than traditional RGB, instead of being 0 -> 255, LSL uses 0 -> 1. <1.0, 1.0, 1.0>, means "white" and <0.0, 0.0, 0.0> means "black": <lsl> // white & opaque

   llSetText("I am white", <1.0, 1.0, 1.0>, 1.0);

</lsl> <lsl> // black & opaque

   llSetText("I am black", ZERO_VECTOR, 1.0);

</lsl> The 1.0 is the alpha setting. 1.0 means fully opaque (alpha), and 0.0 would be completely transparent (invisible): <lsl>

   llSetText("green text with alpha 0.5", <0.0, 1.0, 0.0>, 0.5);
   llSetText("white text with alpha 1.0\nfully opaque", <1.0, 1.0, 1.0>, 1.0);
   llSetText("white text with alpha 1.0\nfully opaque", <1.0, 1.0, 1.0>, 1.0);
   llSetText("invisible black text with alpha 0.0\nfully transparent", ZERO_VECTOR, 0.0);
   llSetText("invisible black text with alpha 0.0\nfully transparent", <0.0, 0.0, 0.0>, 0.0);

</lsl>

Multiple lines

<lsl> // two lines of green text

   llSetText("I am\non two lines!", <0.0, 1.0, 0.0>, 1.0);
</lsl>

Useful Snippets

Drag this script out of inventory onto an object to erase its set text: <lsl> // http://wiki.secondlife.com/wiki/llSetText

default {

   state_entry()
   {
       llSetText("", ZERO_VECTOR, 0.0);     // after removing the float text of the prim
       llRemoveInventory(llGetScriptName());// we remove the script, too
   }

} </lsl> Code to easily specify appearance of hovertext: <lsl> vector blue = <0.0, 0.0, 1.0>; vector orange = <1.0, 0.5, 0.0>; vector cyan = <0.0, 1.0, 1.0>; vector pink = <1.0, 0.5, 0.76>; vector green = <0.0, 1.0, 0.0>; vector red = <1.0, 0.0, 0.0>; vector white = <1.0, 1.0, 1.0>; vector yellow = <1.0, 1.0, 0.1>; vector purple = <1.0, 0.0, 1.0>; vector black = <0.0, 0.0, 0.0>;

string hoverText = "TEXT GOES HERE"; vector hoverColor = white;// set predefined color or any RGB color vector in float form float hoverAlpha = 1.0; // Sets the text's transparency, 1.0 being opaque, while 0.0 would be transparent

default {

   state_entry()
   {
       llSetText(hoverText, hoverColor, hoverAlpha);
   }

} </lsl> To make hovertext under linked prims you can use this simple function: <lsl> mySetLinkText(integer linknum, string text, vector color, float alpha) {

   llSetLinkPrimitiveParamsFast(linknum, [PRIM_TEXT, text, color, alpha]);

}

// For example:

default {

   touch_start(integer total_number)
   {
       mySetLinkText(LINK_SET, "TEST", <0,1,0>, 0.5);
   }

} </lsl>

Notes

To actually display text on a prim, see XyzzyText, or consider using parcel prim Media options (useful only if you have control over the land's media settings.)


The function displays text that hover over the prim's center, the prim position. The height over the center is proportional to the prim's Z-dimension exclusively

  • It doesn't matter how the prim is rotated, so if Z is smaller than X and Y the text may be seen on the prim

See Also

Constants

•  PRIM_TEXT

Articles

•  Limits SL limits and constrictions
•  Color in LSL
•  Translucent Color
•  Examples: SplitLine Insert 'new line' escape codes at certain positions of a string
•  Useful snippet: llGetObjectPermMask Label an object with text and newlines to give away or sell

Deep Notes

Footnotes

  1. ^ Floating text with an alpha set to 0.0 is rendered "invisible"

Signature

function void llSetText( string text, vector color, float alpha );