Hi, Kimmo Hämäläinen wrote: > I'm using behaviour paths for moving items on the screen but I have > noticed that for dragging items a plain set_position(x,y) produces a > better (smoother) result. However, the behaviour path animation still > makes sense when moving the items without dragging (i.e. when scrolling > a page forward). Now, for set_position(x,y) I need to know the x and y, > and the only way to get them is to animate an actor along the behaviour > path, at the same time recording the coordinates of the actor, which > takes some time even with advance() + start().
I am not sure I understand correctly what you are trying to do, particularly why you need to call clutter_actor_set_position() on an actor that has its position driven by a behaviour. Could you explain a bit more please, maybe a code fragment ? Tomas -- To unsubscribe send a mail to [EMAIL PROTECTED]
