[
https://issues.apache.org/jira/browse/FLEX-21243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13587228#comment-13587228
]
Tim John commented on FLEX-21243:
---------------------------------
I disagree with this resolution. There is a difference between an effect being
stopped and an effect ending. End implies the effect has reached its
conclusion, and some listeners will need to be fired on this condition only.
In the current behaviour, stopping an effect to prevent it from reaching its
conclusion and triggering the next step in an application, triggers the next
step regardless.
Strictly speaking the behaviour should be reversed, so that the effectStop
event be dispatched on Effect.stop() and with effectEnd, because in both cases
the effect has stopped.
> Effect dispatchs effectEnd event when it calls effect.stop method.
> ------------------------------------------------------------------
>
> Key: FLEX-21243
> URL: https://issues.apache.org/jira/browse/FLEX-21243
> Project: Apache Flex
> Issue Type: Bug
> Components: Effects
> Affects Versions: Adobe Flex SDK Previous
> Environment: Affected OS(s): Windows
> Affected OS(s):
> Browser: Internet Explorer 8.x
> Language Found: Japanese
> Reporter: Adobe JIRA
> Assignee: Adobe JIRA
>
> Steps to reproduce:
> 1. run an attached mxml source with debug mode
> 2. click "rotate" button
> 3. click "rotate" button again during running effect
>
> Actual Results:
> effectEnd event is dispatched by effect.stop method
>
> Expected Results:
> effectEnd event should not be dispatched by effect.stop method
>
>
> Workaround (if any):
--
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
