Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page

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?


[ Usenet FAQs | Search | Web FAQs | Documents | RFC Index ]

316) How do I debug X protocol errors (e.g., BadWindow, BadMatch) in


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



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 | Search | Web FAQs | Documents | RFC Index ]

Send corrections/additions to the FAQ Maintainer:
kenton@rahul.net (Ken Lee)

Last Update May 13 2007 @ 00:23 AM