DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L1894 Version: 1.3-current I also think less (modifications) is better, especially in the fltk1.x branch. This is why I suggested first this idea of unregistering the parent before deletion first. As far as I recall, the auto pointers can solve invalid deletion problems at the cost of adding more ref. counting hassle, to handle them and still may not prevent the need of taking care of some parent/children side effects manually. IHMO, it could indeed be sufficient to document the side effects occuring when static widgets are used in groups, and it makes sense to give the developer the responsibility of removing them before the group does it as there is no way to detect/distinguish them from dynamically created widgets. Link: http://www.fltk.org/str.php?L1894 Version: 1.3-current _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
