Parent document is top of "Motif FAQ (Part 9 of 9)"
Previous document is "345) If a single widget has multiple callback functions, are they"
Next document is "347) If I call XtGetValues on a resource that does not exist for a"
346) Why are some widgets still visible after I call
XtDestroyWidget() on them?
[Last modified: Nov 96]
Answer: To avoid memory corruption problems, the X Toolkit uses a 2 phase
destroy process. When you call XtDestroyWidget(), the widgets are not really
destroyed until after you return to the Xt main loop. Until then, the widget
will behave (mostly) as if they were not destroyed. If this is a problem, you
should unmanage them as well (you can safely unmanage them after you destroy
them and before you return to the main loop).
Ken Lee, http://www.rahul.net/kenton/
Note: The details of the two-phase destruction are described on the
XtCreateWidget(3Xt)/XtDestroyWidget(3Xt) man page. - ksall@cen.com
Parent document is top of "Motif FAQ (Part 9 of 9)"
Previous document is "345) If a single widget has multiple callback functions, are they"
Next document is "347) If I call XtGetValues on a resource that does not exist for a"