docs/bugs.txt

   1 wxWindows Buglist
   2 -----------------
   3
   4 Until the wxWindows bug database is up and running, please add
   5 entries in this style:
   6
   7 BUG NUMBER:
   8 SHORT DESCRIPTION:
   9 DETAILS:
  10 WORKAROUND:
  11 wxWINDOWS VERSION:
  12 PLATFORM(S):
  13 DATE IDENTIFIED:
  14 IDENTIFIED BY:
  15 DATE FIXED:
  16 FIXED BY:
  17
  18 -------------------------START OF BUGLIST-------------------------
  19
  20 BUG NUMBER:             1
  21 SHORT DESCRIPTION:      Popup menu bug
  22 DETAILS:
  23 If a popup wxMenu is destroyed after its parent window has been
  24 destroyed, we get the message "Object XXX does not have windowed
  25 ancestor".
  26 Possible fix: call menu->DestroyMenu() before deleting the window,
  27 if the window knows about the menu that was last popped up (hard
  28 to know this with confidence).
  29 WORKAROUND:
  30 Delete the menu before deleting the window on which it
  31 was popped up.
  32 wxWINDOWS VERSION:      2.0.1
  33 PLATFORM(S):            wxMotif
  34 DATE IDENTIFIED:        ?/?/1998
  35 IDENTIFIED BY:          Julian Smart <julian.smart@ukonline.co.uk>
  36 DATE FIXED:
  37 FIXED BY:
  38
  39 BUG NUMBER:             2
  40 SHORT DESCRIPTION:      Misc. Motif bugs
  41 DETAILS:
  42 - In wxGrid, cell highlight is not drawn/erased properly.
  43
  44 - Setting the size of a hidden window may show that window.
  45
  46 - wxRadioBox sometimes doesn't show (e.g. in controls sample).
  47
  48 - Can't set the colours for the buttons in the file selector, for
  49   some reason.
  50
  51 - On SGI IRIX 6.4, XtDestroyWidget in ~wxWindow causes a crash in
  52   some cicumstances. This is being looked into. Meanwhile, a
  53   possible workaround is to remove the final XtDestroyWidget line in ~wxWindow
  54   (window.cpp). This will mean that child windows will only get
  55   destroyed when frames and dialogs are destroyed, so dynamic subwindow
  56   deletion may not work properly.
  57
  58 - There are reports that scrolling can cause crashes under Lesstif.
  59   This is probably a Lesstif bug.
  60 WORKAROUND:
  61 wxWINDOWS VERSION:      2.0.1
  62 PLATFORM(S):            wxMotif
  63 DATE IDENTIFIED:        ?/?/1999
  64 IDENTIFIED BY:          Julian Smart
  65 DATE FIXED:
  66 FIXED BY:
  67
  68 BUG NUMBER:             3
  69 SHORT DESCRIPTION:      Dialog Editor issues
  70 DETAILS:
  71 Dialog Editor could be more user-friendly. Controls are hard to
  72 size and position accurately. No way of changing tab order
  73 except by editing .wxr file.
  74 WORKAROUND:
  75 wxWINDOWS VERSION:      2.0.1
  76 PLATFORM(S):            All
  77 DATE IDENTIFIED:        ?/?/1998
  78 IDENTIFIED BY:          Julian Smart <julian.smart@ukonline.co.uk>
  79 DATE FIXED:
  80 FIXED BY:
  81
  82 BUG NUMBER:             4
  83 SHORT DESCRIPTION: Appending a menuitem with negative id causes menu not to be shown
  84 DETAILS: I haven't tested it throughly, though it happens when appending a submenu
  85 WORKAROUND: Add dummy id number even for menuitems which don't require them (submenus for example)
  86 wxWINDOWS VERSION: 2.1.11
  87 PLATFORMS: wxGTK
  88 DATE IDENTIFIED: 10/11/1999
  89 IDENTIFIED BY: Jonathan Brown <jbrown@sso.sytexinc.com>
  90
  91 BUG NUMBER:             5
  92 SHORT DESCRIPTION: no vertical space inside wxHTML
  93 DETAILS: We are working on making a demonstration of projects we do here
  94 using Python & wxWindows & HTML (wxPython/wxHTML thus). We 'd like to
  95 have the opportunity to specify vertical space, eg <br><br>, or <p><p>
  96 in HTML. These constructs currently do not work. I looked in the source
  97 code (nice job btw), but am not sure where to hack the solution. I
  98 am willing to discuss this in more detail.
  99 WORKAROUND: Create a transparent gif of 1x1 pixel and use width & height
 100 to fool the renderer
 101 wxWINDOWS VERSION: wxWindows 2.1.11
 102 PLATFORMS: Windows + Python 1.5
 103 DATE IDENTIFIED: 10/11/1999
 104 IDENTIFIED BY: A.T.Hofkamp
 105 DATE FIXED: 11/11/1999
 106 FIXED BY: Vaclav Slavik
 107
 108 BUG NUMBER:             6
 109 SHORT DESCRIPTION: MSWindows Paths in include files
 110 DETAILS: I may be wrong, but it looks like all the paths in the
 111 include files are based on a unix system. The problem is when
 112 you go to compile VC++6 can't find any of the other includes it
 113 needs. [Note from JACS: VC++ accepts forward slashes so
 114 there must be a setup problem.]
 115 WORKAROUND: Change all the paths in the includes
 116 wxWINDOWS VERSION: 2.1.11
 117 PLATFORMS: wxMSW
 118 DATE IDENTIFIED: 11/11/1999
 119 IDENTIFIED BY: Mark A Russell <markarussell@earthlink.net>
 120
 121
 122
 123 ---------------------------END OF BUGLIST-------------------------
 124
 125