[ Usenet FAQs | Web FAQs | Documents | RFC Index ]
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
Top Document: Motif FAQ (Part 9 of 9)
Previous Document: 340) If a single widget has multiple callback functions, are they
Next Document: 342) If I call XtGetValues on a resource that does not exist for a
-
Search the FAQ Archives
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
Top Document: Motif FAQ (Part 9 of 9)
Previous Document: 340) If a single widget has multiple callback functions, are they
Next Document: 342) If I call XtGetValues on a resource that does not exist for a
341) 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 Note: The details of the two-phase destruction are described on the XtCreateWidget(3Xt)/XtDestroyWidget(3Xt) man page. - ksall@cen.com
Top Document: Motif FAQ (Part 9 of 9)
Previous Document: 340) If a single widget has multiple callback functions, are they
Next Document: 342) If I call XtGetValues on a resource that does not exist for a
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
[ Usenet FAQs | Web FAQs | Documents | RFC Index ]
Send corrections/additions to the FAQ Maintainer:
kenton@rahul.net (Ken Lee)
Last Update October 22 2009 @ 05:27 AM