Re: How to do animations in 1.16
- From: Alessandro Re <ale ale-re net>
- To: Emmanuele Bassi <ebassi gmail com>
- Cc: "clutter-list gnome org" <clutter-list gnome org>
- Subject: Re: How to do animations in 1.16
- Date: Wed, 16 Oct 2013 02:34:56 +0200
Hello,
On Wed, Oct 16, 2013 at 12:39 AM, Emmanuele Bassi <ebassi gmail com> wrote:
the only thing that should be noted is that
Clutter.Transition.set_animatable() should never be used directly with
actors: you should use Clutter.Actor.add_transition(), which handles a
lot of the internal state, like signal emissions and automatic
collection of stopped/completed transitions, and allows you to access
transitions from the actor instead of keeping the instance around.
Clutter.Transition.set_animatable() is just a bit of implementation
that I had to let escape, in order to allow external implementations
for non-actor types.
Roger! If you don't mind, I'll add this note to the tutorial :)
On 15 October 2013 23:32, Bastian Winkler <buz netbuz org> wrote:
Apart from the deprecated methods (Actor.animate(), Animator, State) you
have two different APIs for animations, implicit and explicit.
Both ways are documented here:
https://developer.gnome.org/clutter/stable/ClutterActor.html#ClutterActor-animation
Uh, thanks for this. I thought (for some obscure reason) that implicit
animation was indissolubly related to ClutterAnimation and with its
deprecation the implicit method was also deprecated. Good to know it
is not!
True again, ClutterTransition is an abstract class. This should be
really mentioned in the docs. Would you mind to open a bug report?
I don't mind. Bug 710232 opened.
You have to prefix names of the virtual methods with 'do_'. PyGObject
restriction...
Oh, thanks. (I really have to take a look at GObject)
Well, the :position property uses ClutterPoint, but you're setting
integer values... :)
Ouch :( sorry. Anyway, no error is printed about this (is it ok?)
Using the following it works:
start_pt = clu.Point()
end_pt = clu.Point()
start_pt.x, start_pt.y = 0, 0
end_pt.x, end_pt.y = 100, 100
transition.set_from(start_pt)
transition.set_to(end_pt)
but the code is a bit verbose... Is there a method to create directly
a point with given x and y?
In general, I'm still not sure about how Clutter structures should/can
be created and initialized in python... I remember I found something
on the doc about this topic, but I found it inconsistent with code
experiments, so I just started trying.
I do not know where to go from here.
Can someone please help me?
from gi.repository import Clutter
...
Clutter.main()
This is going to help a lot! Many thanks!
PS: I don't want to sound rude, but would you mind to use 'Clutter'
instead of 'clu' in your tutorial? The former is the usual way for
PyGObject projects, so it would be 'easier' to read for people that are
used to it :)
Of course I don't mind; already modified (with search and replace,
hope it's fine).
Thanks again
~Ale
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]