
| Key: |
SVC-2367
|
| Type: |
New Feature
|
| Status: |
Open
|
| Priority: |
Normal
|
| Assignee: |
Unassigned
|
| Reporter: |
darling brody
|
| Votes: |
34
|
| Watchers: |
13
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Issue Links:
|
Duplicate
|
|
|
|
This issue is original of duplicate:
|
|
|
SVC-3209 In the conquest to reduce the number of scripts in a linkset: new functions llSetLinkText and llLinkTargetOmega
|
|
|
|
|
MISC-2994
llSetLinkText - allow use of setting text to link prim
|
|
|
|
|
Relates
|
|
This issue Relates to:
|
|
|
MISC-268 LSL Features: llGetLink*()/llSetLink*() extensions
|
|
|
|
|
|
This issue is related to by:
|
|
|
|
|
 |
|
SVC-4418 llGetPrimitiveParams is not returning the new SLICE values
|
|
|
|
|
|
SVC-301 Meta-issue: New LSL Functions
|
|
|
|
|
|
|
We have llSetLinkColour, llSetLinkTexture, llSetLinkPrimitiveParams, but we still cant set the floating text on another prim in the set without putting a script in it, thus forcing us to put scripts into child prims just to set the floating text.
I suggest two new commands :-
1) llSetLinkText(integer LinkNumber, string Text, vector Color, float Alpha);
2) llSetLinkPrimitiveParams to have a new command added [integer FLOATING_TEXT, string Text, vector Color, float Alpha]
The advantage of this is to lower the number of scripts in an object (especialy HUDs) which will make region crossings more stable, teleporting safer, and lower the script lag in a region because we dont need all those extra scripts just for setting the floating text.
---------------------------
Additionally we need the following commands to complete the floating text function set
string llGetText(key ID) <--- returns the floating text from the object properties.
when llGetLinkPrimitiveParams() is inplemented their should also be a matching command to read the text.
It should be noted that the ability to read the text will save memory and processing. A function can be assiged to a button in an object via the text it is showing, and then read back from the root prim in the touch event, without needing to store a list of which button had what text on it. Why store something a second time in the script when it is stored in the object already? All we need is the ability to read it back.
Darling.
|
|
Description
|
We have llSetLinkColour, llSetLinkTexture, llSetLinkPrimitiveParams, but we still cant set the floating text on another prim in the set without putting a script in it, thus forcing us to put scripts into child prims just to set the floating text.
I suggest two new commands :-
1) llSetLinkText(integer LinkNumber, string Text, vector Color, float Alpha);
2) llSetLinkPrimitiveParams to have a new command added [integer FLOATING_TEXT, string Text, vector Color, float Alpha]
The advantage of this is to lower the number of scripts in an object (especialy HUDs) which will make region crossings more stable, teleporting safer, and lower the script lag in a region because we dont need all those extra scripts just for setting the floating text.
---------------------------
Additionally we need the following commands to complete the floating text function set
string llGetText(key ID) <--- returns the floating text from the object properties.
when llGetLinkPrimitiveParams() is inplemented their should also be a matching command to read the text.
It should be noted that the ability to read the text will save memory and processing. A function can be assiged to a button in an object via the text it is showing, and then read back from the root prim in the touch event, without needing to store a list of which button had what text on it. Why store something a second time in the script when it is stored in the object already? All we need is the ability to read it back.
Darling. |
Show » |
made changes - 18/May/08 01:08 PM
| Field |
Original Value |
New Value |
|
Summary
|
llSetLinkText or a SET_TEXT option for llSetPrimitiveParams
|
llSetLinkText or a FLOATING_TEXT option for llSetLinkPrimitiveParams
|
made changes - 30/Jun/08 02:00 AM
|
Priority
|
Major
[ 3
]
|
Nice to have
[ 6
]
|
made changes - 12/Jul/08 12:35 AM
|
Link
|
|
This issue is related to by SVC-301
[ SVC-301
]
|
made changes - 13/Jul/08 08:04 AM
|
Priority
|
Nice to have
[ 6
]
|
Normal
[ 4
]
|
made changes - 04/Aug/08 12:03 PM
|
Description
|
We have llSetLinkColour, llSetLinkTexture, llSetLinkPrimitiveParams, but we still cant set the floating text on another prim in the set without putting a script in it, thus forcing us to put scripts into child prims just to set the floating text.
I suggest two new commands :-
1) llSetLinkText(integer LinkNumber, string Text, vector Color, float Alpha);
2) llSetLinkPrimitiveParams to have a new command added [integer FLOATING_TEXT, string Text, vector Color, float Alpha]
The advantage of this is to lower the number of scripts in an object (especialy HUDs) which will make region crossings more stable, teleporting safer, and lower the script lag in a region because we dont need all those extra scripts just for setting the floating text.
Darling.
|
We have llSetLinkColour, llSetLinkTexture, llSetLinkPrimitiveParams, but we still cant set the floating text on another prim in the set without putting a script in it, thus forcing us to put scripts into child prims just to set the floating text.
I suggest two new commands :-
1) llSetLinkText(integer LinkNumber, string Text, vector Color, float Alpha);
2) llSetLinkPrimitiveParams to have a new command added [integer FLOATING_TEXT, string Text, vector Color, float Alpha]
The advantage of this is to lower the number of scripts in an object (especialy HUDs) which will make region crossings more stable, teleporting safer, and lower the script lag in a region because we dont need all those extra scripts just for setting the floating text.
---------------------------
Additionally we need the following commands to complete the floating text function set
string llGetText(key ID) <--- returns the floating text from the object properties.
when llGetLinkPrimitiveParams() is inplemented their should also be a matching command to read the text.
It should be noted that the ability to read the text will save memory and processing. A function can be assiged to a button in an object via the text it is showing, and then read back from the root prim in the touch event, without needing to store a list of which button had what text on it. Why store something a second time in the script when it is stored in the object already? All we need is the ability to read it back.
Darling.
|
made changes - 20/Sep/08 08:24 PM
|
Link
|
|
This issue is related to by SVC-3109
[ SVC-3109
]
|
made changes - 09/Oct/08 01:00 PM
|
Link
|
|
This issue is original of duplicate SVC-3209
[ SVC-3209
]
|
made changes - 13/Nov/08 12:05 PM
|
Workflow
|
jira-2007-12-22a
[ 55964
]
|
jira-2008-11-14
[ 81053
]
|
made changes - 13/Nov/08 04:31 PM
|
Workflow
|
jira-2008-11-14
[ 81053
]
|
jira-2008-11-14a
[ 87494
]
|
made changes - 13/Nov/08 04:52 PM
|
Workflow
|
jira-2008-11-14
[ 87494
]
|
jira-2008-11-14a
[ 94016
]
|
made changes - 25/May/09 02:40 AM
|
Link
|
|
This issue is related to by SVC-4302
[ SVC-4302
]
|
made changes - 25/May/09 02:40 AM
|
Link
|
This issue is related to by SVC-4302
[ SVC-4302
]
|
|
made changes - 25/May/09 02:41 AM
|
Link
|
|
This issue Relates to MISC-268
[ MISC-268
]
|
made changes - 20/Jun/09 03:50 AM
|
Link
|
|
This issue is related to by SVC-4418
[ SVC-4418
]
|
made changes - 22/Jun/09 02:09 PM
|
Link
|
|
This issue is original of duplicate MISC-2994
[ MISC-2994
]
|
made changes - 02/Jul/09 06:53 PM
|
Component/s
|
|
Scripts
[ 10043
]
|
|