Hi,
This is a basic question regarding the relationship between the position &
size allocation mechanism to the position updates of actors during
animation.
Using Pyclutter, I've created a composite actor which contains few child
actors, and I've applied the path behaviour on all of them (the children).
However, once I start the timeline, none of the actors move, and I thought
maybe it has something to do with my overriding of the 'allocate' virtual
method of the parent.
It raised a question I'm not sure how to answer:
During animation, does invoking 'allocate' has any effect on the animated
actors ? I mean - from one side - their position is being changed as the
timeline continues so it breaks their previously allocated bounding box, but
on the other hand how should the composite actor delegate the allocate call
to his children ?
>From my experiment, allocate is being repeatedly called once I start the
timeline, so it seems I have a problem with either option I choose:
1. If I ignore the 'allocate' calls to the parent when the animation is in
place - how the children will move ? And if there's some other mechanism to
move them - what will prevent them from "jumping" back to their old
location, once the animation is finished and allocate is called again ?
2. If I allow 'allocate' calls through the animation - what coordinates
should I put in the bounding box ? After all - I'm not responsible for
updating their position during the animation.


So, what's the relation between the two - the change of position by the
animation and the 'allocate' call ? Do they interfere with each other or
built on top of each other ?

Thanks,
  Nati B.

Reply via email to