From 7043a3a1ed52448d2d952cb88cb0f28d75ef021e Mon Sep 17 00:00:00 2001 From: Emmanuele Bassi Date: Fri, 8 Jun 2012 18:39:01 +0100 Subject: [PATCH] docs: Add notes on implicit vs. explicit animations The implicit animations only apply to properties that are documented as 'animatable'; the explicit animations apply to any property defined through GObject or ClutterAnimatable. --- clutter/clutter-actor.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/clutter/clutter-actor.c b/clutter/clutter-actor.c index d1e457c..2cde2b0 100644 --- a/clutter/clutter-actor.c +++ b/clutter/clutter-actor.c @@ -224,7 +224,8 @@ * The implicit animation model of Clutter assumes that all the * changes in an actor state should be gradual and asynchronous; Clutter * will automatically transition an actor's property change between the - * current state and the desired one without manual intervention. + * current state and the desired one without manual intervention, if the + * property is defined to be animatable in its documentation. * By default, in the 1.0 API series, the transition happens with * a duration of zero milliseconds, and the implicit animation is an * opt in feature to retain backwards compatibility. In order to enable @@ -302,6 +303,7 @@ * of an actor between fully opaque and fully transparent, and back, over * a span of 3 seconds. The animation does not begin until it is added to * the actor. + * The explicit animation API applies to all #GObject properties. * The explicit animation API should also be used when using custom * animatable properties for #ClutterAction, #ClutterConstraint, and * #ClutterEffect instances associated to an actor; see the section on -- 2.7.4