Fabien Costantini wrote: > Your need if I understood you is to get a private children feature. > IMHO this can simply be achieved by what you do now, i.e: your target parent > does > not now that you are its child
Well, it _does_ already know its private children ! :-) Look at Fl_Scroll. It includes the scrollbar widgets in its constructor and calls them scrollbar and hscrollbar, resp.. Only the scrollbars didn't know that Fl_Scroll was their parent widget. They had to be entered in its Fl_Group widget. > but the child does with the parent() relation. Yes, now the child knows it, too. > But now we would have the possible to pass any widget to function that deals > wih tree walking ... > >> Maybe we could do both ? > Sure we can and Fl_Widget children() capabilities would simplify some fltk > existing internal code too just now, so it is useful too just out of the box. :-) Albrecht _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
