wxWindows Buglist
-----------------
-wxGTK:
-------
-
-wxMSW:
-------
-
-wxMotif:
---------
-
-- wxNotebook and property list frame do not appear properly when
- first shown.
- Workaround: resize the window (manually or programmatically) to
- make the window appear.
- This also happens with other windows, e.g. the sizer
- dialog in the layout sample.
-
-- wxSashWindow borders aren't repainted properly if the sashtest
- sample is exposed (after being under another window).
-
-- If a popup wxMenu is destroyed after its parent window has been
- destroyed, we get the message "Object XXX does not have windowed
- ancestor".
- Workaround: delete the menu before deleting the window on which it
- was popped up.
- Possible fix: call menu->DestroyMenu() before deleting the window,
- if the window knows about the menu that was last popped up (hard
- to know this with confidence).
+Until the wxWindows bug database is up and running, please add
+entries in this style:
+BUG NUMBER:
+SHORT DESCRIPTION:
+DETAILS:
+WORKAROUND:
+wxWINDOWS VERSION:
+PLATFORM(S):
+DATE IDENTIFIED:
+IDENTIFIED BY:
+DATE FIXED:
+FIXED BY:
+
+-------------------------START OF BUGLIST-------------------------
+
+BUG NUMBER: 1
+SHORT DESCRIPTION: Popup menu bug
+DETAILS:
+If a popup wxMenu is destroyed after its parent window has been
+destroyed, we get the message "Object XXX does not have windowed
+ancestor".
+Possible fix: call menu->DestroyMenu() before deleting the window,
+if the window knows about the menu that was last popped up (hard
+to know this with confidence).
+WORKAROUND:
+Delete the menu before deleting the window on which it
+was popped up.
+wxWINDOWS VERSION: 2.0.1
+PLATFORM(S): wxMotif
+DATE IDENTIFIED: ?/?/1998
+IDENTIFIED BY: Julian Smart <julian.smart@ukonline.co.uk>
+DATE FIXED:
+FIXED BY:
+
+BUG NUMBER: 2
+SHORT DESCRIPTION: Misc. Motif bugs
+DETAILS:
- In wxGrid, cell highlight is not drawn/erased properly.
- Setting the size of a hidden window may show that window.
-General:
---------
+- wxRadioBox sometimes doesn't show (e.g. in controls sample).
+
+- Can't set the colours for the buttons in the file selector, for
+ some reason.
+
+- On SGI IRIX 6.4, XtDestroyWidget in ~wxWindow causes a crash in
+ some cicumstances. This is being looked into. Meanwhile, a
+ possible workaround is to remove the final XtDestroyWidget line in ~wxWindow
+ (window.cpp). This will mean that child windows will only get
+ destroyed when frames and dialogs are destroyed, so dynamic subwindow
+ deletion may not work properly.
+
+- There are reports that scrolling can cause crashes under Lesstif.
+ This is probably a Lesstif bug.
+WORKAROUND:
+wxWINDOWS VERSION: 2.0.1
+PLATFORM(S): wxMotif
+DATE IDENTIFIED: ?/?/1999
+IDENTIFIED BY: Julian Smart
+DATE FIXED:
+FIXED BY:
+
+BUG NUMBER: 3
+SHORT DESCRIPTION: Dialog Editor issues
+DETAILS:
+Dialog Editor could be more user-friendly. Controls are hard to
+size and position accurately. No way of changing tab order
+except by editing .wxr file.
+WORKAROUND:
+wxWINDOWS VERSION: 2.0.1
+PLATFORM(S): All
+DATE IDENTIFIED: ?/?/1998
+IDENTIFIED BY: Julian Smart <julian.smart@ukonline.co.uk>
+DATE FIXED:
+FIXED BY:
+
+BUG NUMBER: 4
+SHORT DESCRIPTION: Appending a menuitem with negative id causes menu not to be shown
+DETAILS: I haven't tested it throughly, though it happens when appending a submenu
+WORKAROUND: Add dummy id number even for menuitems which don't require them (submenus for example)
+wxWINDOWS VERSION: 2.1.11
+PLATFORMS: wxGTK
+DATE IDENTIFIED: 10/11/1999
+IDENTIFIED BY: Jonathan Brown <jbrown@sso.sytexinc.com>
+
+BUG NUMBER: 5
+SHORT DESCRIPTION: no vertical space inside wxHTML
+DETAILS: We are working on making a demonstration of projects we do here
+using Python & wxWindows & HTML (wxPython/wxHTML thus). We 'd like to
+have the opportunity to specify vertical space, eg <br><br>, or <p><p>
+in HTML. These constructs currently do not work. I looked in the source
+code (nice job btw), but am not sure where to hack the solution. I
+am willing to discuss this in more detail.
+WORKAROUND: Create a transparent gif of 1x1 pixel and use width & height
+to fool the renderer
+wxWINDOWS VERSION: wxWindows 2.1.11
+PLATFORMS: Windows + Python 1.5
+DATE IDENTIFIED: 10/11/1999
+IDENTIFIED BY: A.T.Hofkamp
+
+
+---------------------------END OF BUGLIST-------------------------
+