X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/b40b0f5b204d59bbc1d3e66c5bba192b878469a6..c109ef116daa1e8d35f5bba0c0007dcef86c56aa:/docs/bugs.txt diff --git a/docs/bugs.txt b/docs/bugs.txt index 5cfc5f67d9..0e3f60470b 100644 --- a/docs/bugs.txt +++ b/docs/bugs.txt @@ -32,7 +32,7 @@ was popped up. wxWINDOWS VERSION: 2.0.1 PLATFORM(S): wxMotif DATE IDENTIFIED: ?/?/1998 -IDENTIFIED BY: Julian Smart +IDENTIFIED BY: Julian Smart DATE FIXED: FIXED BY: @@ -75,7 +75,7 @@ WORKAROUND: wxWINDOWS VERSION: 2.0.1 PLATFORM(S): All DATE IDENTIFIED: ?/?/1998 -IDENTIFIED BY: Julian Smart +IDENTIFIED BY: Julian Smart DATE FIXED: FIXED BY: @@ -244,7 +244,7 @@ WORKAROUND: visitor_email_address: haneef@symphonyeda.com wxWINDOWS+VERSION: 2.1.12 DATE+FIXED: 29/11/99 -FIXED+BY: Julian Smart +FIXED+BY: Julian Smart DATE+FIXED: DATE+IDENTIFIED: 29/11/1999 @@ -310,6 +310,114 @@ WORKAROUND: visitor_email_address: wxWINDOWS+VERSION: 2.1.11 +DATE+FIXED: 05/01/2000 +DATE+IDENTIFIED: 04/01/2000 +DETAILS: The various message callback members of +wxMessageDialog pass the client_data variable +as in "int" which are later used a pointers. On a 64-bit +system they must be passed as pointers or +as "long" variables. +FIXED+BY: JACS +IDENTIFIED+BY: Ray Lanza +PLATFORMS: motif +SHORT+DESCRIPTION: wxMessageDialog is not 64bit safe +Submit: Submit +WORKAROUND: Change the declaration to void * or long +visitor_email_address: rjl@zk3.dec.com +wxWINDOWS+VERSION: 2.1.10 + +DATE+FIXED: 12/01/2000 +DATE+IDENTIFIED: 12/01/2000 +DETAILS: When I try to Print or create +wxPrintPreview object in the +printing sample, it fails. +The reason is the wxGetDefaultDeviceName +function in file msw/dcprint.cpp. In line 253 +the memory is freed, and then +the pointer to the freed memory +is used. +FIXED+BY: Alexey V. Exarevsky (patched into wxWin 12/1/2000 by JACS) +IDENTIFIED+BY: Alexey V. Exarevsky +PLATFORMS: wxMSW, compiled by VC++ 6.0 +SHORT+DESCRIPTION: Print/Print preveiw to default printer in NT +Submit: Submit +WORKAROUND: I have moved lines that free +memory below the lines that +use lpszDeviceName and +lpszPortName +visitor_email_address: ave@relex.ru +wxWINDOWS+VERSION: 2.1.11 + +DATE+FIXED: +DATE+IDENTIFIED: 14/01/2000 +DETAILS: I run my linux boxes headless and use a Windows box for an XServer... every sample I have tried so far +hangs in a loop tring to get an acceptable font for something or other... here is the GDB trace +#1102 0x40203d19 in wxMessageBox () +#1103 0x401aee31 in wxFontMapper::GetAltForEncoding () +#1104 0x40287c45 in wxLoadQueryNearestFont () +#1105 0x4015b3cc in wxFont::GetInternalFont () +#1106 0x4017d1db in wxWindow::GetTextExtent () +#1107 0x4018f499 in wxDialogBase::CreateTextSizer () +#1108 0x40253302 in wxGenericMessageDialog::wxGenericMessageDialog () +#1109 0x40203d19 in wxMessageBox () +#1110 0x401aee31 in wxFontMapper::GetAltForEncoding () +#1111 0x40287c45 in wxLoadQueryNearestFont () +#1112 0x4015b3cc in wxFont::GetInternalFont () +#1113 0x40154653 in wxWindowDC::DoGetTextExtent () +#1114 0x4015e3fd in wxFrame::OnCreateStatusBar () +#1115 0x4015e17d in wxFrame::CreateStatusBar () +#1116 0x8062edc in ChatFrame::ChatFrame () +#1117 0x8062d3d in ChatClient::OnInit () +#1118 0x4014587e in wxEntry () +#1119 0x401617db in main () +FIXED+BY: +IDENTIFIED+BY: John Barrett +PLATFORMS: wxGTK +SHORT+DESCRIPTION: wxWin/GTK and X-Win32 on Windows +Submit: Submit +WORKAROUND: +visitor_email_address: jbarrett@box100.com +wxWINDOWS+VERSION: 2.1.11 + +DATE+FIXED: +DATE+IDENTIFIED: 17.01.2000 +DETAILS: wxWindows 2 installer simply replaces msv(i)crt.dll. MUST ONLY overwrite if newer!!! Apart from that: the libraries provided are from VC6Sp1 and are known to be buggy! +FIXED+BY: +IDENTIFIED+BY: Klaus Richter +PLATFORMS: wxMSW +SHORT+DESCRIPTION: Windows Installer problem +Submit: Submit +WORKAROUND: Dlls from at least Sp2 (better 3) are needed (read MSDN KB Q190536)! +visitor_email_address: richter@secude.com +wxWINDOWS+VERSION: 2.1.11 + +DATE+FIXED: +DATE+IDENTIFIED: 18/01/2000 +DETAILS: I tested wxWindows/GTK+ with a simple example which +uses frame, menu, and statusbar. But when I selected +a menu item which creates a simple 'about dialog' +several times, the program crashed with segmentation fault. +I traced it with gdb, and I got this message: + +Program received signal SIGSEGV, Segmentation fault +0x408f1796 in match_theme_image () + from /usr/lib/gtk/themes/engines/libpixmap.so + +I guessed from this message that the pixmap routine in +GTK+ theme engine caused crash. So, I changed GTK+ theme +to default which doesn't use any pixmaps and tested +again. This time, the program didn't crash. + +I'm using Redhat 6.1 with egcs 1.1.2. +FIXED+BY: +IDENTIFIED+BY: Sangpil Yoon +PLATFORMS: wxGTK +SHORT+DESCRIPTION: Problem with GTK+ theme +Submit: Submit +WORKAROUND: Currently none. +visitor_email_address: yphil99@yahoo.com +wxWINDOWS+VERSION: 2.1.12 + ---------------------------END OF BUGLIST-------------------------