Search the FAQ Archives

3 - A - B - C - D - E - F - G - H - I - J - K - L - M
N - O - P - Q - R - S - T - U - V - W - X - Y - Z
faqs.org - Internet FAQ Archives

comp.windows.x Frequently Asked Questions (FAQ) 7/7
Section - 154) Why doesn't XtDestroyWidget() actually destroy the widget?

( Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Single Page )
[ Usenet FAQs | Web FAQs | Documents | RFC Index | Counties ]


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?
See reader questions & answers on this topic! - Help others by sharing your knowledge

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.

User Contributions:

Comment about this article, ask questions, or add new information about this topic:



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 March 27 2014 @ 02:12 PM