On Jul 1, 2007, at 9:05 AM, Greg Ercolano wrote: > delete_widget() only *schedules* deletion, which is > actually handled by the FLTK app loop later on when it > thinks it's safe to do so, the widget doesn't get destroyed > immediately. > > remove() just removes the pointer from the parent, > doesn't do any deleting. > > So doing either one first probably doesn't matter, > as long as they're next to each other. (someone feel free > to correct me).
Just to be sure, and just in case the implementation of delete_widget () changes (for example by using a compatibility layer when changing to FLTK2), you should always first remove the widget from its parent and then delete the widget itself. Matthias ---- http://robowerk.com/ _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
