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

Motif FAQ (Part 9 of 9)
Section - 315) Why is XtWindow(widget) == 0?

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


Top Document: Motif FAQ (Part 9 of 9)
Previous Document: 314) Why does the xyz application core dump when I cut and paste?
Next Document: 316) How do I debug X protocol errors (e.g., BadWindow, BadMatch) in
See reader questions & answers on this topic! - Help others by sharing your knowledge
[Last modified: Oct 95]

Answer: The window is not created (and is NULL) until the widget is realized.
In general, using XtWindow() is a bad idea.  In most cases, you can create
more robust code by subclassing the widget and putting your window code in new
wiget class methods.

Ken Lee

User Contributions:

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



Top Document: Motif FAQ (Part 9 of 9)
Previous Document: 314) Why does the xyz application core dump when I cut and paste?
Next Document: 316) How do I debug X protocol errors (e.g., BadWindow, BadMatch) in

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