Dojo Toolkit: Ticket #5462: Remove either the onBegin or beforeBegin event for _Animation <p> 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. </p> <p> Logging this ticket b/c it seems useful and so that I can keep an eye on it. </p> en-us Dojo Toolkit Trac 1.2 dante Sat, 19 Jan 2008 11:16:05 GMT status changed; resolution set <ul> <li><strong>status</strong> changed from <em>new</em> to <em>closed</em> </li> <li><strong>resolution</strong> set to <em>wontfix</em> </li> </ul> <p> matt, this is a wontfix. </p> <p> beforeBeing and onBegin are two different things, with different use cases. </p> <p> beforeBegin fires before the animation ever starts, giving you access too the animation object, and the node for modification immediately before. </p> <p> 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) </p> Ticket ptwobrussell Sat, 19 Jan 2008 16:12:15 GMT <p> Makes perfect sense now that you said it like that. Thanks for clearing that up. </p> Ticket