sl-service-account
commented
11 years ago Lucia Nightfire commented at 2013-05-16T11:17:05Z, updated at 2013-05-16T11:22:19Z
The following script will show the control execution and lack thereof in both cases mentioned above:
Rez two boxes. Resize each to 0.1 meters or smaller. Link both boxes. Save the following script in the child prim. Take and wear as an HUD.
Init()
{
session = 0;
llSetText("",<1.0,1.0,1.0>,1.0);
llRequestPermissions(llGetOwner(),!!llGetAttached() * PERMISSION_TAKE_CONTROLS);
}
integer session;
default
{
state_entry()
{
Init();
}
on_rez(integer start_param)
{
Init();
}
touch_start(integer total_number)
{
Init();
}
run_time_permissions(integer permissions)
{
if (permissions)
{
llTakeControls(DEBUG_CHANNEL,TRUE,TRUE);
}
}
control(key name, integer levels, integer edges)
{
llSetText("Session: " + (string)(++session) + "\nLevels: " + (string)levels + "\nEdges: " + (string)edges,<1.0,1.0,1.0>,1.0);
}
}
User Story
Seems that the release on the RC channels has brought about an annoying bug that effects control event triggering in attachment's child prims after changing regions.
There are two different effects depending how you enter a version 13.05.14.275813 RC region.
After going into an RC region while using any controls, those controls will lock under execution and remain locked until you reset the script or the control perms or detach the object.
After going into an RC region without using controls like with a teleport, the control event will not trigger when attempting to use any controls until you re-request/re-grant control perms or go back to a main channel region.
I discovered this today when using my dasher HUD which has been a child prim in my main HUD for several years now.
Original Jira Fields
| Field | Value | | ------------- | ------------- | | Issue | BUG-2601 | | Summary | Issue with control event triggering in attachment's child prims after region change. | | Type | Bug | | Priority | Unset | | Status | Accepted | | Resolution | Accepted | | Reporter | Lucia Nightfire (lucia.nightfire) | | Created at | 2013-05-16T06:09:55Z | | Updated at | 2014-03-15T06:36:22Z | ``` { 'Business Unit': ['Platform'], 'Date of First Response': '2013-05-16T13:05:53.556-0500', 'System': 'SL Simulator', 'Target Viewer Version': 'viewer-development', 'What just happened?': "Seems that the release on the RC channels has brought about an annoying bug that effects control event triggering in attachment's child prims after changing regions.\r\n\r\n\r\nThere are two different effects depending if you are going into an RC version 13.05.14.275813 region or an MC version 13.05.04.275247 region.\r\n\r\nAfter going into an RC region while using any controls, those controls will lock under execution and remain locked until you trigger an event that resets the script or the control perms or detach the object.\r\n\r\nAfter going into an MC region while using any controls or not, the control event will not execute when attempting to use any controls until you trigger an event that resets the script or the control perms.\r\n\r\n \r\n\r\nI discovered this today when using my dasher HUD which has been a child prim in my main HUD for several years now.", 'What were you doing when it happened?': '?', 'What were you expecting to happen instead?': '?', } ```