Difference between revisions of "Talk:LlGetText"
(Created page with "I cannot conceive of any circumstances whereby a script would not have some other way to access the information of the prim property set by llSetText. If nothing else, unless the…") |
|||
| Line 1: | Line 1: | ||
I cannot conceive of any circumstances whereby a script would not have some other way to access the information of the prim property set by llSetText. If nothing else, unless the text was hard-coded into the llSetText parameters, there will be a string variable containing the information. Failing that, it's easy enough to write any scripts that set llSetText so that the text information is also captured in a string variable for later use. Actually, I mis-spoke. I can conceive of one circumstance whereby the llSetText property might be set but there is no way to access a variable, and that is if the object is set no-mod. Otherwise even if you didn't make the object, the first time it's rezzed you can type a notecard and put the text in that, which is then accessible by a script. --[[User:Reynard_Baroque|<span style="background:red;"> </span><span style="color:red"> <b>¥</b> </span><span style="background:red;"> </span><span style="color:gold;background:navy;"> <b>Reynard</b> </span>]] 21:31, 8 April 2011 (PDT) | I cannot conceive of any circumstances whereby a script would not have some other way to access the information of the prim property set by llSetText. If nothing else, unless the text was hard-coded into the llSetText parameters, there will be a string variable containing the information. Failing that, it's easy enough to write any scripts that set llSetText so that the text information is also captured in a string variable for later use. Actually, I mis-spoke. I can conceive of one circumstance whereby the llSetText property might be set but there is no way to access a variable, and that is if the object is set no-mod. Otherwise even if you didn't make the object, the first time it's rezzed you can type a notecard and put the text in that, which is then accessible by a script. --[[User:Reynard_Baroque|<span style="background:red;"> </span><span style="color:red"> <b>¥</b> </span><span style="background:red;"> </span><span style="color:gold;background:navy;"> <b>Reynard</b> </span>]] 21:31, 8 April 2011 (PDT) | ||
:Meant to add the text is available as a prim parameter anyway with llGetPrimitiveParams([ PRIM_TEXT ]); --[[User:Reynard_Baroque|<span style="background:red;"> </span><span style="color:red"> <b>¥</b> </span><span style="background:red;"> </span><span style="color:gold;background:navy;"> <b>Reynard</b> </span>]] 21:40, 8 April 2011 (PDT) | |||
Revision as of 21:40, 8 April 2011
I cannot conceive of any circumstances whereby a script would not have some other way to access the information of the prim property set by llSetText. If nothing else, unless the text was hard-coded into the llSetText parameters, there will be a string variable containing the information. Failing that, it's easy enough to write any scripts that set llSetText so that the text information is also captured in a string variable for later use. Actually, I mis-spoke. I can conceive of one circumstance whereby the llSetText property might be set but there is no way to access a variable, and that is if the object is set no-mod. Otherwise even if you didn't make the object, the first time it's rezzed you can type a notecard and put the text in that, which is then accessible by a script. -- ¥ Reynard 21:31, 8 April 2011 (PDT)
- Meant to add the text is available as a prim parameter anyway with llGetPrimitiveParams([ PRIM_TEXT ]); -- ¥ Reynard 21:40, 8 April 2011 (PDT)