Emmanuele Bassi wrote:
so, apart from the extra-rambly email, I went through three iterations of the patch and at the end I have something similar to your initial approach - plus the removal of the automagic creation of alpha and timeline if NULL is passed to set_alpha() and set_timeline() respectively and some more documentation. you can find it inside the 1.0-integration branch, which will be merged into master before the API frozen release.
How about a little modification to the clutter_actor_animate* functions also? :)
Is there really a good reason to assign only one animation object to an actor and readjust that when the clutter_actor_animate* is called again, instead of creating separate animation objects for each call of the clutter_actor_animate*?
I think most developers do not usually need the pure ClutterAnimation API (as stated in the documentation also), but should use clutter_actor_animate instead. However, because all properties of an actor are sharing the same easing mode, timeline etc., those utility functions are almost useless (as I stated earlier: [1], section II).
It would be easy to modify the behavior of the clutter_actor_animate* functions by changing the quark_object_animation to point a GHashTable of property-animation pairs instead of an animation object directly.
BR, Henrik [1] http://lists.o-hand.com/clutter/2657.html -- Henrik Hedberg - http://www.henrikhedberg.net/ -- To unsubscribe send a mail to [email protected]
