X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/76a4f50db50c618402b6a0b37d1a56af2c00a95f..6ada5c335980d255e2fb315ed86c091010870c5e:/docs/bugs.txt diff --git a/docs/bugs.txt b/docs/bugs.txt index 91846d9b6a..ed68b8c570 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: @@ -49,7 +49,7 @@ DETAILS: some reason. - On SGI IRIX 6.4, XtDestroyWidget in ~wxWindow causes a crash in - some cicumstances. This is being looked into. Meanwhile, a + some circumstances. 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 @@ -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: @@ -207,7 +207,7 @@ DETAILS: Around line 1234 or the common/docview.cpp file following code exists.. if (!theTemplate) theTemplate=templates[FilterIndex] ; -The problem is tat FilterIndex is one based and the templates array is zero based. The correct +The problem is that FilterIndex is one based and the templates array is zero based. The correct thing might be to use FilterIndex-1 as the index. Else the following scenario will cause a crash. @@ -222,13 +222,13 @@ I understand that it is very hard to figure out the template when the user does not select one of the known extensions but -this simple fix might atleast +this simple fix might at least avoid the crash.... I started playing with wxMSW just this morning and have not yet figured out exactly how to -submit a fix. I atleast wanted +submit a fix. I at least wanted to report it. Besides what I do for the MSW might not be correct for the other platforms :-) @@ -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 @@ -292,7 +292,7 @@ output to freeze when the limit was reached. FIXED+BY: Vasu Harish IDENTIFIED+BY: Vasu Harish PLATFORMS: wxMSW -SHORT+DESCRIPTION: wxTextCtrl clogs output occassionally when the text size limit is reached +SHORT+DESCRIPTION: wxTextCtrl clogs output occasionally when the text size limit is reached WORKAROUND: In the check for (len > limit) condition in wxTextCtrl::AdjustSpaceLimit() call, added the condition to check for the len==limit. visitor_email_address: vasuh@bullant.net @@ -339,7 +339,7 @@ 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 +SHORT+DESCRIPTION: Print/Print preview to default printer in NT Submit: Submit WORKAROUND: I have moved lines that free memory below the lines that @@ -351,7 +351,7 @@ 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 +hangs in a loop trying 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 () @@ -379,6 +379,44 @@ 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-------------------------