FWIW here are my 2 cents.
The most difficult problem you´ll face is how to react if a "frame"
gets dropped. Slower machines may not be up to the challenge to render
a complicated animation, or if the user has many apps open at the same
time (and mail is starting to download many emails in the background
for example) the animation might start to stutter. So it is a good
idea to compute where the control must be located at the given point
in time. I have done many experiments with this and some of the
results went into animationEngines AEMoveTo handler. That one will
tackle dropped frames and position the moving objects correctly to the
given point in time. The next version of ae will have this for the
other moving methods too.
Hope that helps a bit,
Malte_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
