[...] > It's easy to do spacing with a minimal subroutine to save current > positions, add some pixels, or do anything you like.
I though that was the goal of Fl_Pack here. But ok. > Don't write > coordinates literally - that *will* become a nightmare if you want > to add widgets later. Did you look at fluid for interactive layout? > Personally I don't use it, but lots of users do. It can use a grid > setup value (or similar, don't know) to aid you in positioning on > rows and columns, e.g. set it to 5, and fluid will only position > on every 5'th pixel (Menu: Layout/Grid and Size Settings (Ctrl+g)). I look at it but it did not attract me a lot. In this case I prefer manual coding. (Adding flPlug for a less static callback managment) > > Where's the problem? This looks perfectly well to me and works > for me (tested). See attached code. I did only add the headers > and the main function, and I changed *only* the initial window > size. The button part was the problem. A little bit tricky to have the good values the first try. At least Fl_Pack hide a good part of the job. Its seems that there is a preference for Fl_Group than Fl_Pack. I am wondering if Motif use this king of "pack" object itself. By the way, thanks for your time. I will continue to explore fltk. _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
