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 - 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 | Forum ]


Top Document: Motif FAQ (Part 9 of 9)
Previous Document: 315) Why is XtWindow(widget) == 0?
Next Document: 317) Why doesn't XtNameToWidget (widget, "MyName") work?
See reader questions & answers on this topic! - Help others by sharing your knowledge
Motif applications?

[Last modified: Jun 98]
Answer: For a general tutorial on X protocol errors, see:

http://www.rahul.net/kenton/perrors.html


Here are two common problems.  First, if you get a BadWindow error showing a
0x0 window ID, you're probably calling XtWindow() on a widget that is not
realized.  See the previous subject.

Second, a BadMatch error often indicates that the depth of a window or a
pixmap is not correct.  You could be using a depth 1 pixmap when you should be
using a pixmap with the depth of the associated window.  Or, you could be
creating a new shell with a depth that does not match its visual type or
colormap.

Ken Lee

User Contributions:

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

CAPTCHA




Top Document: Motif FAQ (Part 9 of 9)
Previous Document: 315) Why is XtWindow(widget) == 0?
Next Document: 317) Why doesn't XtNameToWidget (widget, "MyName") work?

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