On 10 May 2011, at 21:55, Matthias Melcher wrote: > > FLTK 1 always places in relation to the next higher window, not group (for > compatibility reasons). FLTK 2 places relative to the group.
Yup - Robark has been around here a while, I guess he knows that really... but just wishes it were not so some times... As to how you might work around it, is it possible to derive your own container widget from Fl_Group, and then override the add() method such that it takes in the widget you pass it, determines the widget's x,y co-ords, adds on it's own x,y co-ords then does a widget->position(newx,newy) before actually calling the base class add() on the widget... Something like that might work, at least for widgets that you explicitly add() to your group... Not sure how it would fly with widgets that were implicitly added to your group by the group->begin()/end() stuff though. Anyone have a view on that? Robert - is that any good to you? -- Ian _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
