Here's some state change events, http://pastebin.com/Kx4X2MZx.
I looked into the Transition class and it's not an event dispatcher. You
can see how the transitions work by looking at commitCurrentState() in the
UIComponent class. It looks like all the events are dispatched there.
The extra event that I was referring to might have been the UPDATE or
REPEAT event in the Animation class:
switch (eventType) {
case EffectEvent.EFFECT_START:
_animationTarget.animationStart(this);
break;
case EffectEvent.EFFECT_END:
_animationTarget.animationEnd(this);
break;
case EffectEvent.EFFECT_STOP:
_animationTarget.animationStop(this);
break;
case EffectEvent.EFFECT_REPEAT:
_animationTarget.animationRepeat(this);
break;
case EffectEvent.EFFECT_UPDATE:
// here for completeness; usually handled in sendUpdateEvent
_animationTarget.animationUpdate(this);
break;
}
IIRC I noticed somewhere along the line the UPDATE or REPEAT events were
not getting re dispatched on one or some of the sub classes. I can't find
it now so maybe it was fixed in an update.
On Wed, Nov 23, 2016 at 4:12 PM, bilbosax <[email protected]> wrote:
> Thanks for looking into it Jude. I was just a little surprised when I was
> looking at the events available for s:State and s:Transition and I didn't
> see an obvious "transitionComplete" type of event available. I think there
> is one available for view states, just not traditional states.
>
>
>
> --
> View this message in context: http://apache-flex-users.23333
> 46.n4.nabble.com/Event-Fired-When-A-Transition-is-Complete-t
> p14202p14212.html
> Sent from the Apache Flex Users mailing list archive at Nabble.com.
>
