Current bugs or misbehaviours
-----------------------------

* Drawing on wxToolBar doesn't work like the original version since
  the buttons and toggles are X widgets and clutter the drawing area.
  The tool bar is a bit larger (4 pixels) because of the shadow around
  the tools to show pressed and depressed state.
  I did not implement the following methods because they don't have
  any sense for me:
      void SpringUpButton(int index)
      void DrawTool(wxMemoryDC& memDC, wxToolBarTool *tool)
  use X version instead (wxSetup: USE_XT_VERSION = 0) if you need
  this behaviour.

* To select/unselect an item in user edit mode, you must hit the "real"
  widget or the "frame". The "real" widget is e.g. the list of a listbox but
  not the the scrollbar. The "frame" is usally the widget containing the
  label.
    A bit strange is the behaviour of radio boxes since they are a
  composition of toggle widgets inside a group widget. Events occuring
  inside the toggles are not dispatched by wxWindows but by XToolkit, i.e.
  they may not be intercepted for panel item placement.

* OnItemLeftClick and OnItemRightClick won't be called when OnItemEvent
  is overriden. It is currently not really possible to override the panel item
  placement.
  BUT: It is the same with the standard wxWindows distribution.

* If a menu is popped up the frame looses the focus. This results in a call to
  OnActivate(FALSE) during the menu selection and a OnActivate(TRUE) after the
  selection is done. Currently I don't know, how to fix this since the
  XFocusEvents don't give the pair of windows between which the focus is
  changed. So I don't know, if a FocusOut/FocusIn remains in a frame.
  !!! This is NOT true for the MENUBAR. The menubar does not grab the keyboard!

* OnCharHook works for wxRadioBoxes only if you use X11R6
  (XlibSpecificationRelease > 5), because I need XtDispatchEventToWidget
  to propagate a key event to a widget't parent.

* PrologIO seems only to work with flex/bison correctly. Something is wrong,
  but that's not a problem of wxXt alone.

* wxPostScriptDC scaling behaves exactly as the wxWindowDC scaling. This is
  a feature, not a bug. Because of this, you must not use SetDeviceOrigin
  on a wxPostScriptDC. SetLogicalScale, SetLogicalOrigin and SetUserScale
  behave exactly as for wxWindowDC.

* For wxGrid you have to set the colours *AFTER* creation again. I could not
  find the mistake...

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

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

