]>
Commit | Line | Data |
---|---|---|
1 | wxWindows Buglist | |
2 | ----------------- | |
3 | ||
4 | wxGTK: | |
5 | ------ | |
6 | ||
7 | - It is impossible to reposition a window before showing it | |
8 | on screen. Suspected GTK bug. | |
9 | ||
10 | - DnD does only moderately work. | |
11 | ||
12 | wxMSW: | |
13 | ------ | |
14 | ||
15 | - TODO | |
16 | ||
17 | wxMotif: | |
18 | -------- | |
19 | ||
20 | - If a popup wxMenu is destroyed after its parent window has been | |
21 | destroyed, we get the message "Object XXX does not have windowed | |
22 | ancestor". | |
23 | Workaround: delete the menu before deleting the window on which it | |
24 | was popped up. | |
25 | Possible fix: call menu->DestroyMenu() before deleting the window, | |
26 | if the window knows about the menu that was last popped up (hard | |
27 | to know this with confidence). | |
28 | ||
29 | - In wxGrid, cell highlight is not drawn/erased properly. | |
30 | ||
31 | - Setting the size of a hidden window may show that window. | |
32 | ||
33 | - wxRadioBox sometimes doesn't show (e.g. in controls sample). | |
34 | ||
35 | - Can't set the colours for the buttons in the file selector, for | |
36 | some reason. | |
37 | ||
38 | - On SGI IRIX 6.4, XtDestroyWidget in ~wxWindow causes a crash in | |
39 | some cicumstances. This is being looked into. Meanwhile, a | |
40 | possible workaround is to remove the final XtDestroyWidget line in ~wxWindow | |
41 | (window.cpp). This will mean that child windows will only get | |
42 | destroyed when frames and dialogs are destroyed, so dynamic subwindow | |
43 | deletion may not work properly. | |
44 | ||
45 | - There are reports that scrolling can cause crashes under Lesstif. | |
46 | This is probably a Lesstif bug. | |
47 | ||
48 | General: | |
49 | -------- | |
50 | ||
51 | - Dialog Editor could be more user-friendly. Controls are hard to | |
52 | size and position accurately. No way of changing tab order | |
53 | except by editing .wxr file. | |
54 |