Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#5462 closed enhancement (wontfix)

Remove either the onBegin or beforeBegin event for _Animation

Reported by: ptwobrussell Owned by: dante
Priority: low Milestone:
Component: fx Version: 1.0
Keywords: Cc: [email protected]…, Bryan Forbes
Blocked By: Blocking:


Given that there is a beforeBegin event and an onBegin event, I can't fathom a use case for how both of these could be useful. Seems that one of them should go so that the API for _Animation is as clear as it possibly can be.

Logging this ticket b/c it seems useful and so that I can keep an eye on it.

Change History (2)

comment:1 Changed 14 years ago by dante

Resolution: wontfix
Status: newclosed

matt, this is a wontfix.

beforeBeing and onBegin are two different things, with different use cases.

beforeBegin fires before the animation ever starts, giving you access too the animation object, and the node for modification immediately before.

onBegin fires after the animation has begun cycling, so in effect is somewhat asynchronous. If you want to fire two animations simultaneously without using combine (or can't use combine/chain) you can set the onBegin to trigger another action _AS_ the animation is starting (rather than before, and preventively)

comment:2 Changed 14 years ago by ptwobrussell

Makes perfect sense now that you said it like that. Thanks for clearing that up.

Note: See TracTickets for help on using tickets.