[ Usenet FAQs | Web FAQs | Documents | RFC Index ]
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Single Page
Top Document: comp.windows.x Frequently Asked Questions (FAQ) 7/7
Previous Document: 153) Are callbacks guaranteed to be called in the order registered?
Next Document: 155) How can I open multiple displays with Xt?
-
Search the FAQ Archives
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Single Page
Top Document: comp.windows.x Frequently Asked Questions (FAQ) 7/7
Previous Document: 153) Are callbacks guaranteed to be called in the order registered?
Next Document: 155) How can I open multiple displays with Xt?
154) Why doesn't XtDestroyWidget() actually destroy the widget?
XtDestroyWidget() operates in two passes, in order to avoid leaving dangling data structures; the function-call marks the widget, which is not actually destroyed until your program returns to its event-loop.
Top Document: comp.windows.x Frequently Asked Questions (FAQ) 7/7
Previous Document: 153) Are callbacks guaranteed to be called in the order registered?
Next Document: 155) How can I open multiple displays with Xt?
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Single Page
[ Usenet FAQs | Web FAQs | Documents | RFC Index ]
Send corrections/additions to the FAQ Maintainer:
faq%craft@uunet.uu.net (X FAQ maintenance address)
Last Update October 22 2009 @ 05:36 AM