Difference between revisions of "Template:Issues/SVC-3017"

Latest revision as of 20:47, 2 February 2010

A

Server drops first touch event when a script returns to a state with a touch_start handler

When changing from a state that lacks a touch event into a state that has a touch event, the first touch will be dropped; this effects all three touch events (touch_start, touch, touch_end). See: SVC-3017

@@ Line 1: / Line 1: @@
 {{Issues|SVC-3017|Server drops first {{LSLGC|Touch|touch}} event when a script returns to a {{LSLGC|State|state}} with a [[touch_start]] handler|type=bug}}{{#if:
-{{#vardefine:notes|{{#var:notes}}
+{{#vardefine:caveats|{{#var:caveats}}
-Do not change states from within the [[touch_start]]() event, since this will prevent the [[touch_end]]() event being called even if you did not define it and from this preserve a partial solve touch event chain across state transitions. To perform state transitions at a "touch" make use of the [[touch_end]]() event instead!  See: [https://jira.secondlife.com/browse/SVC-3017  SVC-3017]
+* When changing from a state that lacks a {{LSLGC|Touch|touch}} [[event]] into a [[state]] that has a touch event, the first touch will be dropped; this effects all three touch events ([[touch_start]], [[touch]], [[touch_end]]). See: {{Jira|SVC-3017}}
+<!--
+* If the [[state]] is changed within either a [[touch_start]] or [[touch]] event, the [[touch_end]] event will not be triggered in either the source state or target state. See: {{Jira|SVC-3017}}
+-->
 }}
 }}<noinclude>
-{{Box|Notes|{{#var:notes}}}}
+{{Box|Caveats|{{#var:caveats}}}}
 </noinclude>