-
Emmanuele Bassi authored
ClutterAnimation uses the weak ref machinery of GObject when associated to ClutterActor by clutter_actor_animate() and friends - all the while taking a reference on the actor itself. In order to trigger the weak ref callback, external code would need to unref the Actor at least twice, which has slim chance of happening. Plus, the way to destroy an Actor is to call destroy(), not call unref(). The destruction sequence of ClutterActor emits the ::destroy signal, which should be used by classes to release external references the might be holding. My oh my, this sounds *exactly* the case! So, let's switch to using the ::destroy signal for clutter_actor_animate() and friends, since we know that the object bound to the Animation is an Actor, and has a ::destroy signal. This change has the added benefit of allowing destroying an actor as the result of the Animation::completed signal without getting a segfault or other bad things to happen. Obviously, the change does no...
57ebce80