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
+DATE FIXED: 11/11/1999
+FIXED BY: Vaclav Slavik
+
+BUG NUMBER: 6
+SHORT DESCRIPTION: wxGTK-2.1.11 fails to build under IRIX
+DETAILS: Seems we have a section that says, if we're not Sun, Linux, or
+FreeBSD, then there's something very wrong...
+c++ -c -MMD -D__WXGTK__ -DGTK_NO_CHECK_CASTS -D_REENTRANT -D_IODBC_ -O2
+-I. -I./include -I./include
+-I./src/zlib -I./src/png -I./src/jpeg
+-I/home/rhh/software/gtk+-1.2.3/include
+-I/home/rhh/software/glib-1.2.3/lib/glib/include
+-I/home/rhh/software/glib-1.2.3/include -Wall
+-D"wxINSTALL_PREFIX=\"/home/rhh/software/wxGTK-2.1.11\"" -fPIC -o
+dialup.o ./src/unix/dialup.cpp ./src/unix/dialup.cpp: In method `int
+wxDialUpManagerImpl::CheckIfconfig()':
+./src/unix/dialup.cpp:500: warning: ignoring pragma: warning
+./src/unix/dialup.cpp:527: parse error before `;'
+./src/unix/dialup.cpp:544: confused by earlier errors, bailing out gmake:
+*** [dialup.o] Error 1
+wxWINDOWS VERSION: 2.1.11
+PLATFORMS: wxGTK
+DATE IDENTIFIED: 16/11/1999
+IDENTIFIED BY: Randall Hopper
+
+DATE+FIXED:
+DATE+IDENTIFIED: 11-15-99
+DETAILS: I am a new user. I downloaded setup.exe and setup.wXX then ran the install program. It prompted me for disk two which puzzled me. There was no obvious solution.
+FIXED+BY:
+IDENTIFIED+BY: William Deans
+PLATFORMS: wxWindows
+SHORT+DESCRIPTION: misnamed setup.wXX files prevents install
+Submit: Submit
+WORKAROUND: The problem seems to be that the default download name for the setup.wXX files is not 'setup.wXX' but instead 'setup.wXX..wXX' Every new user who installs could change these names... but why not simply change them on the server? (I was using IE 5 under Windows 98)
+visitor_email_address: willdeans@mindspring.com
+wxWINDOWS+VERSION: Current version as of 11-15-99
+
+DATE+FIXED:
+DATE+IDENTIFIED: 11-15-99
+DETAILS: to recreate:
+ click "new dialog" several times
+ view the properties of a dialog box
+ DO NOT CLOSE THE PROPERTIES BOX
+ click on another dialog in the list
+ right click the new dialog and select view properties..... (THE PROPERTY BOX DOES NOT CHANGE EVEN THOUGH IT SHOULD!... BUT THIS IS NOT THE CRASH)
+ to make the crash click the Name property in the properties dialog box -- the application crashes
+FIXED+BY:
+IDENTIFIED+BY: William Deans
+PLATFORMS: wxWindows
+SHORT+DESCRIPTION: dialog editor CRASHES
+Submit: Submit
+WORKAROUND: be sure and close the properties box every time before switching to a new dialog... this might be hard to remember as the properties box does not stay in front of the dialog editor........ as I feel that it should
+visitor_email_address: willdeans@mindspring.com
+wxWINDOWS+VERSION: 2.1.11 (Current version as of 11-15-99)
+
+DATE+FIXED:
+DATE+IDENTIFIED: 11-15-99
+DETAILS: to recreate:
+ click "Dialogs" folder to the left
+ select delete from the menu
+FIXED+BY:
+IDENTIFIED+BY: William Deans
+PLATFORMS: wxWindows
+SHORT+DESCRIPTION: Dialog Editor CRASHES (again)
+Submit: Submit
+WORKAROUND:
+visitor_email_address: willdeans@mindspring.com
+wxWINDOWS+VERSION: 2.1.11 (Current version as of 11-15-99)
+
+DATE+FIXED:
+DATE+IDENTIFIED: 11-15-99
+DETAILS: to recreate:
+ go to properties (of any dialog)
+ select id
+ select ...
+ hit cancel
+ the property box hangs
+FIXED+BY:
+IDENTIFIED+BY: William Deans
+PLATFORMS: wxWindows
+SHORT+DESCRIPTION: Dialog Editor HANGS
+Submit: Submit
+WORKAROUND:
+visitor_email_address: willdeans@mindspring.com
+wxWINDOWS+VERSION: 2.1.11 (Current version as of 11-15-99)
+
+DATE+FIXED:
+DATE+IDENTIFIED: 11-15-99
+DETAILS: to recreate:
+ put a space into the name field of the property box...... this should be disallowed, but is not
+FIXED+BY:
+IDENTIFIED+BY: William Deans
+PLATFORMS: wxWindows
+SHORT+DESCRIPTION: Dialog Editor Creates Files It Cannot Parse
+Submit: Submit
+WORKAROUND: each time a change is made to a dialog..... that section of the wxr file should be written to a buffer and re-parsed..... if the parsing fails the change should be disallowed
+visitor_email_address: willdeans@mindspring.com
+wxWINDOWS+VERSION: 2.1.11 (Current version as of 11-15-99)
+
+DATE+IDENTIFIED: 26/11/1999
+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
+thing might be to use FilterIndex-1 as the index. Else the following scenario will
+cause a crash.
+
+1. Use the docvsmdi example
+2. Bring up the file open dlg.
+3. Select Files of Type "Text"
+4. c:\autoexec.bat for file name
+5. Press okay and you should see
+ the crash.
+
+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
+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
+to report it. Besides what I do
+for the MSW might not be correct
+for the other platforms :-)
+
+Note from JACS: fixed (I hope) by making m_filterIndex
+zero-based in MSW wxFileDialog implementation
+(it's zero-based in wxGTK/the generic dialog).
+
+IDENTIFIED+BY: Haneef Mohammed
+PLATFORMS: wxMSW
+SHORT+DESCRIPTION: Bug in wxDocTemplate::SelectDocumentPath()
+WORKAROUND:
+visitor_email_address: haneef@symphonyeda.com
+wxWINDOWS+VERSION: 2.1.12
+DATE+FIXED: 29/11/99
+FIXED+BY: Julian Smart <julian.smart@ukonline.co.uk>
+
+DATE+FIXED:
+DATE+IDENTIFIED: 29/11/1999
+DETAILS: wxGTK cannot seem to find the default font
+on (some?) Debian 2.x systems. This results
+in infinite recursion in wxLoadQueryNearestFont.
+
+It only happens on one of my two Debian machines,
+but I haven't investigated thoroughly enough to give
+any more detail.
+
+I have made a temporary workaround by trapping
+recursion in wxLoadQueryNearestFont with a static
+bool flag.
+
+I will investigate the problem further if this bug has
+not already been reported by someone else.
+FIXED+BY: Vadim, just after 2.1.11?
+IDENTIFIED+BY: Tom Marshall
+PLATFORMS: wxGTK
+SHORT+DESCRIPTION: wxGTK: infinite recursion in font selection
+WORKAROUND: Create default font mapping for every
+wxGTK app (?)
+visitor_email_address: tommy@aa.net
+wxWINDOWS+VERSION: 2.1.11
+
+DATE+FIXED:
+DATE+IDENTIFIED: 29/11/1999
+DETAILS: If the listening socket cannot be obtained
+(ie, TIME_WAIT) the wxsocket server example
+program segfaults.
+FIXED+BY:
+IDENTIFIED+BY: Tom Marshall
+PLATFORMS: wxGTK
+SHORT+DESCRIPTION: wxGTK: wxsocket example crashes if listen socket unavailable
+WORKAROUND: None.
+visitor_email_address: tommy@aa.net
+wxWINDOWS+VERSION: 2.1.11
+
+DATE+FIXED: 07/12/1999
+DATE+IDENTIFIED: 04/12/1999
+DETAILS: In wxTextCtrl::AdjustSpaceLimit(), the check for len > limit
+does not take into account when len == limit. This caused the
+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
+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
+wxWINDOWS+VERSION: wx2.1.11
+
---------------------------END OF BUGLIST-------------------------
projects / wxWidgets.git / blobdiff