sl-service-account
commented
9 years ago Lucia Nightfire commented at 2015-08-20T02:58:16Z
I thought of this on occasion as well, strictly to get away from the rez then attach redundancy instead of just attach from object inventory.
My concerns are permissions validating and updating issues primarily with permissions hierachy (objects of one permission with contents with different permissions) as well as objects that have active slam bits for new owner.
I also wonder if there are any concerns of use over no rez land when called from an attachment which would bypass current restrictions with llAttachToAvatarTemp().
How would you like the feature to work?
integer llAttachObjectToAvatarTemp(string object, integer attach_point)
Works much like llAttachToAvatarTemp except attaches a object from the object's inventory.
returns TRUE if success or a flag if no success that describes the reason
Why is this feature important to you? How would it benefit the community?
I am developing a Sim using the new Experience tools in SL.
One of the problems I am having, is attaching HUDs to users in a fast and reliable manner.
Unfortunately, as it stands right now, I have to choose between speed and reliability - I cannot have both;
For speed, my distributor script can rez the HUD then say in chat who it should attach to. This fails in reliability as the HUD may take too long to rez and miss the message.
For reliability, I can write a Key-Value-Pair to the database, containing a 'Rez ID' integer as Key and AvatarUUID as Value, pass the RezID as a start-param to the rezzed HUD and then have the rezzed HUD read the KVP to figure out the UUID of the avatar to attach to. Whilst this is more reliable, this is slower, and pointlessly writing and reading to the database for data that should not be entering persistent storage.
Thus, I feel to make a smoother experience, a new function is required that allows Experience creators the ability to directly attach HUD's from a central distributor to an avatar without all that... funny business, in between.
Thank you for considering this. ^^
Links
Related
Original Jira Fields
| Field | Value | | ------------- | ------------- | | Issue | BUG-9933 | | Summary | Add llAttachObjectToAvatarTemp | | Type | New Feature Request | | Priority | Unset | | Status | Closed | | Resolution | Unactionable | | Reporter | Extrude Ragu (extrude.ragu) | | Created at | 2015-08-20T01:15:18Z | | Updated at | 2023-03-15T18:15:16Z | ``` { 'Business Unit': ['Platform'], 'Date of First Response': '2015-08-19T21:58:16.430-0500', 'How would you like the feature to work?': "integer llAttachObjectToAvatarTemp(string object, integer attach_point)\r\n\r\nWorks much like llAttachToAvatarTemp except attaches a object from the object's inventory.\r\n\r\nreturns TRUE if success or a flag if no success that describes the reason", 'ReOpened Count': 0.0, 'Severity': 'Unset', 'Target Viewer Version': 'viewer-development', 'Why is this feature important to you? How would it benefit the community?': "I am developing a Sim using the new Experience tools in SL.\r\n\r\nOne of the problems I am having, is attaching HUDs to users in a fast and reliable manner.\r\n\r\nUnfortunately, as it stands right now, I have to choose between speed and reliability - I cannot have both;\r\n\r\nFor speed, my distributor script can rez the HUD then say in chat who it should attach to.\r\nThis fails in reliability as the HUD may take too long to rez and miss the message.\r\n\r\nFor reliability, I can write a Key-Value-Pair to the database, containing a 'Rez ID' integer as Key and AvatarUUID as Value, pass the RezID as a start-param to the rezzed HUD and then have the rezzed HUD read the KVP to figure out the UUID of the avatar to attach to.\r\nWhilst this is more reliable, this is slower, and pointlessly writing and reading to the database for data that should not be entering persistent storage.\r\n\r\nThus, I feel to make a smoother experience, a new function is required that allows Experience creators the ability to directly attach HUD's from a central distributor to an avatar without all that... funny business, in between.\r\n\r\nThank you for considering this. ^^", } ```