Hello! 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().
Would it make sense to add some new clutter API to get the path coordinates given the frame of the timeline? It would save me the effort of travelling the path in advance. This would make sense at least in bspline, ellipse, and path behaviours. BR, Kimmo -- To unsubscribe send a mail to [EMAIL PROTECTED]
