> AlbrechtS and Fabien discussion snipped. I don't think this addresses Albrecht's current need to handle events from outside the current group's boundaries, and maybe it's too much of a change, but for future consideration...
Rather than using a Composite (in the Design Patterns sense) would it not be possible to extend the current children idea so that there are "actual" children and "adopted" children. The "actual" children are permanent features within the widget, such as horizonal and vertical scroll bars within a generic scroll widget, or ok and cancel buttons within a generic dialog widget and may be shown or hidden but not removed by the user. The "adopted" children would be the widgets that the user is really interested in, such as the contents of the scroll area or dialog, and could be added and removed as required. This gets round the current situation where some children may be "special" and are expected to be at the start or end of the children() list, or which can't be removed, etc. D. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
