SLJiraStats Bug: SVC-5170 |
|
| SVC-5170 | New primtiveparam: PRIM_NAME | | Reporter: | kelly linden |
| Assignee: | kelly linden |
| Votes: | 20 |
| Environment: | |
| Status: | Fix Pending |
| Resolution: | Unresolved |
| Created: | 2009-12-23 13:56:48-05 |
| Updated: | 2010-07-12 17:59:05-04 |
| Linden ID: | DEV-48189 |
| Components: | |
| |
| Comments |
WarKirby Magojiro 2009-12-25 14:48:04-05 a PRIM_NAME parameter for set/get linkprimitiveparams will undoubtedly lead to usage of this field as data storage. I don't see any problem wiht that personally, and the system should be designed on the assumption of every prim using the maximum length value for this field in any case.
| Cheshyr Pontchartrain 2010-02-11 12:01:56-05 Agreed. It's not a bad thing since the system must host that data anyway. And frankly, I already do this via child scripts for data that must survive a script reset. Not having to use child scripts will be a boon.
| Michelle Resistance 2010-03-08 18:10:01-05 PRIM_TEXT will give us some of this functionality, assuming we set it to completely transparent.
Gotta remember to encrypt or otherwise obfuscate that data, though, since it's still probably accessible to the client with some work.
Same goes for PRIM_NAME and PRIM_DESC used as data storage.
| Jolanda Undercroft 2010-03-18 07:51:35-04 well, PRIM_NAME and PRIM_DESC for llSetLinkPrimitiveParams would save me a lot of scripts that cause LAG
| Lamorna Proctor 2010-03-23 05:42:01-04 Yes PLEASE 
| Stickman Ingmann 2010-03-27 12:46:55-04 PRIM_NAME and PRIM_DESC won't make it into 1.38, but possibly 1.40.
From: http://wiki.secondlife.com/wiki/User:Babbage_Linden/Office_Hours/2010_01_20
[3:23] Babbage Linden: we have some other changes in the backlog
[3:23] Babbage Linden: but they are unlikely to get done before 1.38 ships
[3:24] Babbage Linden: including llLinkParticleSystem
[3:24] Babbage Linden: * PRIM_NAME, PRIM_DESC
[3:24] Babbage Linden: llAvatarOnLinkSitTarget / llLinkSitTarget
(Note that llLinkParticleSystem did actually make it into 1.38)
| Ilana Debevec 2010-03-28 16:17:00-04 @Stickman
actually
from: http://wiki.secondlife.com/wiki/User:Babbage_Linden/Office_Hours/2010_03_10
[03:26] Ilana Debevec: PRIM_NAME and PRIM_DESC were on the list almost from the beginning, on https://jira.secondlife.com/browse/SVC-5165
[03:26] Latif Khalifa: Babbage, since it's near the top of the list for may scripters PRIM_NAME and PRIM_DESC for get/set linked prim params, is it feasable for them to get into 1.40, I cannot imagine them being to difficult to implement
[03:26] Babbage Linden: they might have been on a list 
[03:27] Babbage Linden: and no, I don't see them as being hard, so I'll see what I can do
there may be hope
| Mo Noel 2010-04-13 03:11:43-04 I dearly need this feature to 'port' my products, as I do multiple prim manipulation and need to manipulate the exactly correct prims all times, whether new links joined or unlinked.
| Lamorna Proctor 2010-04-13 03:56:12-04 Mo, as someone else reminded me on another thread, llGetLinkName has existed since Adam was a lad. Unfortunately, however, there is no llSetLinkName or llGet/SetLinkDesc, so PRIM_NAME and PRIM_DESC would still be valuable.
| kelly linden 2010-07-12 17:59:05-04 In Server 1.40
|
|