How to find a bug and how to report it
--------------------------------------

wxWindows is a nice library to cover GUI- and platform-dependent data
structures and functions. It provides an easy-to-use API and makes the
programmer platform independent.

BUT!

wxWindows only covers the underlying API. This means to the wxWindows
Xt port:

	+----------------+
	| wxWindows      |
	|    + ----------+
	|    +  XToolkit |
	|    + ----------+
	|    +  Xlib     |
	+----+-----------+

If everything is all right, you never have to care about it, but if an
error occurs it may be important to know, what has happened to
XToolkit and Xlib. You need to know which event has caused the error
to know where the it started.

I've added a command line option to the wxWindows library, to trace
the incoming events with the widgets they are delivered to (name and
id). This helps to track which widget (= wxWindow) caused the problem.

Look for the README for the commandline options that help for the
debugging.

If you send me bug report I need at least to know:

 - the wxWindow / Widget
 - the X event
 - a piece of code if possible.

-------------------------------------------------------------------------------
Markus Holzem
Schlossparkstrasse 3
D-52072 Aachen
GERMANY

VOICE: +49 (241) 14145
EMAIL: mho@comnets.rwth-aachen.de

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Note:
For the later versions of wxXt, starting with 1.67, please send bug
reports also to Wolfram Gloger (wmglo@dent.med.uni-muenchen.de).
Thanks !
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
