More about the sizer changes

[wxWidgets.git] / wxPython / docs / CHANGES.txt

diff --git a/wxPython/docs/CHANGES.txt b/wxPython/docs/CHANGES.txt
index b1d028aced207108effc28e244489535d355907d..d13758551e5f9c848c611bf9b1cbcc5991e0237c 100644 (file)
--- a/wxPython/docs/CHANGES.txt
+++ b/wxPython/docs/CHANGES.txt
@@ -1,13 +1,29 @@
-CHANGES.txt for wxPython
+Recent Changes for wxPython
 =====================================================================
 
-2.5.1.1
+2.5.1.6
 -------
 
-(See also the MigrationGuide.txt file for details about some of the
+wx.ADJUST_MINSIZE is now the default behaviour for window items in
+sizers.  This means that the item's GetAdjustedBestSize will be called
+when calculating layout and the return value from that will be used
+for the minimum size.  Added wx.FIXED_MINSIZE flag for when you would
+like the old behavior but you should only need it when your desired
+size is smaller than the item's GetBestSize.  When a window is added
+to a sizer it's initial size, if any, is set as the window's minimal
+size using SetSizeHints if there isn't already a minimal size.
+
+
+2.5.1.5
+-------
+
+(See also the MigrationGuide_ file for details about some of the
 big changes that have happened in this release and how you should
 adapt your code.)
 
+.. _MigrationGuide: MigrationGuide.html
+
+
 The wxWindows project and library is now known as wxWidgets.  Please
 see http://www.wxwindows.org/name.htm for more details.  This won't
 really affect wxPython all that much, other than the fact that the
@@ -96,18 +112,20 @@ and other PyWin32 modules!  This should eliminate the cronic problems
 that have resulted from minor mismatches in how PyWin32 handles the
 GIL and tstate when making callbacks, etc.  The older iewin module
 will be left in this release as the new stuff is not fully backwards
-compatible, but you should migrate your code to the wx.activex version
-of IEHtmlWindow, or the implementation in wx.lib.iewin, so the old one
-can be eventually removed.  Additionally, I've always considered that
-the wx.lib.activexwrapper module is an ugly hack that I only included
-in the lib because I couldn't figure out anything better.  Well now we
-have something that, if it isn't already, has the potential to be
-better.  So consider migrating away from using activexwrapper as well.
-Please see the MigrationGuide for more details on using the new
-module.
+compatible, but you should migrate your code to the new IEHtmlWindow
+in wx.lib.iewin, so the old one can be eventually removed.
+Additionally, I've always considered that the wx.lib.activexwrapper
+module is an ugly hack that I only included in the lib because I
+couldn't figure out anything better.  Well now we have something that,
+if it isn't already, has the potential to be better.  So consider
+migrating away from using activexwrapper as well.  Please see the
+MigrationGuide for more details on using the new module.
 
 .. _wxActiveX: http://members.optusnet.com.au/~blackpaw1/wxactivex.html
 
+Floats are allowed again as function parameters where ints are expected.
+
+
 
 
 2.4.2.4