[
https://issues.apache.org/jira/browse/FLEX-14766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean resolved FLEX-14766.
----------------------------------
Resolution: Fixed
Fix Version/s: Apache Flex 4.10.0
checked into 4.10 develop branch
> Creating a tween with duration zero can remove random playing tween
> -------------------------------------------------------------------
>
> Key: FLEX-14766
> URL: https://issues.apache.org/jira/browse/FLEX-14766
> Project: Apache Flex
> Issue Type: Bug
> Components: Effects
> Affects Versions: Adobe Flex SDK 3.0 (Release)
> Environment: Affected OS(s): All OS Platforms
> Affected OS(s): All OS Platforms
> Language Found: English
> Reporter: Adobe JIRA
> Fix For: Apache Flex 4.10.0
>
>
> Steps to reproduce:
> Create code which:
> 1. Plays a long tween effect with code which listens for an END_EFFECT event
> 2. During the effect, starts a new tween effect with a duration of zero
>
> Actual Results:
> END_EFFECT event is not triggered.
>
> Expected Results:
> END_EFFECT is called
>
> Workaround (if any):
> Never play tween effects with a duration of zero.
> A more serious impact of this bug is orphaned drag/drop items.
> To repro:
> 1. Play a tween effect of duration 0 during a drag/drop drop animation (on or
> off a valid target)
> Actual Results:
> Drag/drop item is orphaned, drag drop tween is never finished. Lots of
> strange state problems. DragImage, if present, will be left on the screen.
> Expected results:
> Drag/drop item is removed correctly, tween is finished.
> Fix:
> Change line 298 of tween.as from this:
> private var id:int;
> to this:
> private var id:int = -1;
> Analysis:
> In endTween() in tween.as around line 526:
> // If tween has been added, id >= 0
> // but if duration = 0, this might not be the case.
> if (id >= 0)
> Tween.removeTweenAt(id);
> This code indicates that an author suspects this bug might be a problem.
> Because new tweens are created with id=0, this remove call removes some
> random other tween currently playing.
> This problem is also present in Flex 2
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
