fixed modal dialogs after event loop change

[wxWidgets.git] / wxPython / CHANGES.txt

diff --git a/wxPython/CHANGES.txt b/wxPython/CHANGES.txt
index 5d81424b18977c32e2dfc75d4119e31dfd23cf6d..156b77310fde2674e1a8d6753e3fb506167c2114 100644 (file)
--- a/wxPython/CHANGES.txt
+++ b/wxPython/CHANGES.txt
@@ -2,6 +2,45 @@ CHANGES.txt for wxPython
 
 ----------------------------------------------------------------------
 
+2.5.0.x
+-------
+
+Many, many little fixes, changes and additions done as part of the move
+to wxWindows 2.5 that I have forgotten about.
+
+Changed the import-startup-bootstrap process employed by wxPython such
+that wxWindows and the underlying gui toolkit are not initialized
+until the wxApp object is created (but before wxApp.OnInit is called.)
+This was required because of changes made to the C++ wxApp class.
+There are both benefits and potential problems with this change.  The
+benefits are that you can import wxPython without requiring access to
+a GUI (for checking version numbers, etc.) and that in a
+multi-threaded environment the thread that creates the app object will
+now be the GUI thread instead of the one that imports wxPython.  Some
+potential problems are that the C++ side of the "stock-objects"
+(wxBLUE_PEN, wxTheColourDatabase, etc.) are not initialized until the
+wxApp object is created, so you should not use them until then.  Also,
+you will probably not be able to do any kind of GUI operation unless
+you have an app object first, (even on Windows where most anything was
+possible beofre.)
+
+Added wxMirrorDC.
+
+Added wxIconLocation
+
+wxPython's setup.py script now expects to use existing libraries for
+the contribs (gizmos, stc, xrc, etc.) rather than building local
+copies of them.
+
+Added Python wrappers for the new wxVScrolledWindow, wxVListBox, and
+wxHtmlListBox classes.
+
+Added wrappers for wxBookCtrl and wxListbook.  wxNotebook now derives
+from wxBookCtrl.
+
+
+
+
 2.4.1.x
 -------