Thanks for all your helpful sample code. I will try to implement it without inheriting from ClutterGroup. However, I am still not sure about the animations:
- Can I use things like clutter_effect_move/ClutterBehaviourPath to animate the movements when changing a sizer? Or would I use a ClutterTimeline and call queue_relayout and interpolate the position in the get_allocation() of my layout manager? - Is it possible to still use set_position() on the children? Let's say I have a "random sizer" which would place new children randomly, but it would allow the user to drag elements around using the mouse (and possibly use a physics/collision detection library to move other actors of the container out of the way using animation). Usually I simply call set_position() in that case, but I don't know what to do if there's a layout manager involved. Thanks, Thomas P.S.: Sorry for always replying to the people directly first and not to the group. I always forget to hit the reply all button... On Thu, Dec 25, 2008 at 1:17 PM, Emmanuele Bassi <[email protected]> wrote: > On Thu, 2008-12-25 at 12:24 +0100, Thomas Steinacher wrote: >> I am not calling allocate on the children in my SizedGroup because I >> would like to be able to switch the sizer of a SizedGroup dynamically >> using an animation (there could be a grid sizer, random sizer etc.), >> and I am not sure if that can be done using allocate. > > what you want is a "pluggable" layout manager, an object the defines the > allocation policy on a container actor. inside the ::allocate > implementation you ask the layout manager object to compute the new > allocation depending on animations, ad hoc rules, etc., like: -- To unsubscribe send a mail to [email protected]
