I'm trying to make sense out of the animator API. They seem to have an excess of attributes and events regarding the state of the animation. In particular, why do we need `start` and `started` which seem rather confused: setting `start` will set `started` but not `start` and will send `onstarted` but not `onstart`; both `start` and `onstart` will eventually be sent when the animator actually starts, but this seems backwards to me.
Attributes: start -- you set this to say you want the animator to start, but it won't have that value until the animator actually does start started -- this reflects the value you _tried_ to set in `start`? paused -- you can set this to temporarily pause the animation isactive -- this is read-only and will be true if the animation started but didn't stop yet Events: onstart -- sent when the animator actually starts (but not when it repeats, despite the documentation) onstarted -- sent when you set the `start` attribute! onpaused -- sent when you set the `paused` attribute onrepeat -- sent each time the animator repeats onstop -- sent when the animator stops Does anyone else find the start/started logic confusing?
