• All submissions to this site are governed by Second Life Project Contribution Agreement. By submitting patches and other information using this site, you acknowledge that you have read, understood, and agreed to those terms.
Issue Details (XML | Word | Printable)

Key: MISC-268
Type: New Feature New Feature
Status: Open Open
Priority: Normal Normal
Assignee: Unassigned
Reporter: Kaluura Boa
Votes: 44
Watchers: 16
Operations

If you were logged in you would be able to see more operations.
4. Second Life Misc Issues - MISC

LSL Features: llGetLink*()/llSetLink*() extensions

Created: 06/Jun/07 08:25 AM   Updated: 12/Aug/09 11:11 PM
Return to search
Component/s: None
Affects Version/s: None
Fix Version/s: None

Issue Links:
Relates
 


 Description  « Hide
I realized that the informations a root prim can know about its linked children is very close from zero:

llGetLinkKey()
llGetLinkName()
llGetLinkNumber()

And that's all. On the other hand, you can totally alter a linked child from the root prim:

llSetLinkAlpha()
llSetLinkColor()
llSetLinkTexture()
llSetLinkPrimitiveParams()

What I would like to have in LSL is:

*llGetLinkAlpha()*
*llGetLinkColor()*
*llGetLinkPos()*
*llGetLinkPrimitiveParams()* (This one would be the bare minimum.)
*llGetLinkRot()*
*llGetLinkTexture()*
*llOffsetLinkTexture()*
*llRotateLinkTexture()*
*llSetLinkText()* (Would be very useful for texts on HUD buttons!)
*llSetLinkTextureAnim()*

And eventually --though we already have llSetLinkPrimitiveParams():

*llSetLinkPos()*
*llSetLinkRot()*

Why? Because the only way to move/rotate children prims is either to hardcode their positions and rotations in the root prim script(s), or else to add a script in every of the children prims. IMO, it's very illogical that the root prim can change the position and rotation of its children but that only them can determine their relative position and rotation. (The same applies to the alpha, color and texture.)



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Rob Linden made changes - 30/Jun/07 10:15 PM
Field Original Value New Value
Workflow jira [ 12073 ] jira-clone [ 12821 ]
Rob Linden made changes - 30/Jun/07 10:19 PM
Workflow jira-clone [ 12821 ] jira [ 13172 ]
McCabe Maxsted made changes - 11/Jul/07 06:57 AM
Link This issue is related to by SVC-301 [ SVC-301 ]
SignpostMarv Martin made changes - 26/Sep/07 04:53 PM
Link This issue is related to by SVC-706 [ SVC-706 ]
SignpostMarv Martin made changes - 26/Sep/07 04:55 PM
Link This issue is related to by SVC-301 [ SVC-301 ]
Rob Linden made changes - 21/Dec/07 11:08 PM
Workflow jira [ 13172 ] jira-2007-12-19 [ 18079 ]
Rob Linden made changes - 21/Dec/07 11:23 PM
Workflow jira [ 18079 ] jira-2007-12-19 [ 18805 ]
Rob Linden made changes - 22/Dec/07 12:37 AM
Workflow jira-2007-12-19 [ 18805 ] jira-2007-12-21 [ 19733 ]
Rob Linden made changes - 23/Dec/07 12:58 AM
Workflow jira-2007-12-21 [ 19733 ] jira-2007-12-22a [ 50018 ]
Tomm Olifone made changes - 23/Oct/08 10:44 PM
Description I realized that the informations a root prim can know about its linked children is very close from zero:
 
 llGetLinkKey()
 llGetLinkName()
 llGetLinkNumber()
 
 And that's all. On the other hand, you can totally alter a linked child from the root prim:
 
 llSetLinkAlpha()
 llSetLinkColor()
 llSetLinkTexture()
 llSetLinkPrimitiveParams()
 
 What I would like to have in LSL is:
 
 **llGetLinkAlpha()**
 **llGetLinkColor()**
 **llGetLinkPos()**
 **llGetLinkPrimitiveParams()** (This one would be the bare minimum.)
 **llGetLinkRot()**
 **llGetLinkTexture()**
 **llOffsetLinkTexture()**
 **llRotateLinkTexture()**
 **llSetLinkText()** (Would be very useful for texts on HUD buttons!)
 
 And eventually --though we already have llSetLinkPrimitiveParams():
 
 **llSetLinkPos()**
 **llSetLinkRot()**
 
 Why? Because the only way to move/rotate children prims is either to hardcode their positions and rotations in the root prim script(s), or else to add a script in every of the children prims. IMO, it's very illogical that the root prim can change the position and rotation of its children but that only them can determine their relative position and rotation. (The same applies to the alpha, color and texture.)
I realized that the informations a root prim can know about its linked children is very close from zero:
 
 llGetLinkKey()
 llGetLinkName()
 llGetLinkNumber()
 
 And that's all. On the other hand, you can totally alter a linked child from the root prim:
 
 llSetLinkAlpha()
 llSetLinkColor()
 llSetLinkTexture()
 llSetLinkPrimitiveParams()
 
 What I would like to have in LSL is:
 
 **llGetLinkAlpha()**
 **llGetLinkColor()**
 **llGetLinkPos()**
 **llGetLinkPrimitiveParams()** (This one would be the bare minimum.)
 **llGetLinkRot()**
 **llGetLinkTexture()**
 **llOffsetLinkTexture()**
 **llRotateLinkTexture()**
 **llSetLinkText()** (Would be very useful for texts on HUD buttons!)
 **llSetLinkTextureAnim()**
 
 And eventually --though we already have llSetLinkPrimitiveParams():
 
 **llSetLinkPos()**
 **llSetLinkRot()**
 
 Why? Because the only way to move/rotate children prims is either to hardcode their positions and rotations in the root prim script(s), or else to add a script in every of the children prims. IMO, it's very illogical that the root prim can change the position and rotation of its children but that only them can determine their relative position and rotation. (The same applies to the alpha, color and texture.)
Sue Linden made changes - 13/Nov/08 11:36 AM
Workflow jira-2007-12-22a [ 50018 ] jira-2008-11-14 [ 74210 ]
Sue Linden made changes - 13/Nov/08 11:51 AM
Workflow jira-2007-12-22a [ 74210 ] jira-2008-11-14 [ 78398 ]
Sue Linden made changes - 13/Nov/08 04:17 PM
Workflow jira-2008-11-14 [ 78398 ] jira-2008-11-14a [ 83433 ]
Chalice Yao made changes - 25/May/09 02:41 AM
Link This issue is related to by SVC-4302 [ SVC-4302 ]
Chalice Yao made changes - 25/May/09 02:41 AM
Link This issue is related to by SVC-2367 [ SVC-2367 ]
Chalice Yao made changes - 25/May/09 02:46 AM
Link This issue is related to by SVC-224 [ SVC-224 ]
Chalice Yao made changes - 25/May/09 02:56 AM
Link This issue Relates to SVC-3360 [ SVC-3360 ]
Chalice Yao made changes - 25/May/09 02:57 AM
Link This issue Relates to SVC-3360 [ SVC-3360 ]
Chalice Yao made changes - 25/May/09 02:57 AM
Link This issue is related to by SVC-3360 [ SVC-3360 ]
Chalice Yao made changes - 10/Jun/09 07:16 AM
Link This issue is related to by SVC-4245 [ SVC-4245 ]
Stickman Ingmann made changes - 12/Aug/09 11:11 PM
Link This issue is related to by MISC-3077 [ MISC-3077 ]