X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/89c876de1cdd247f061e6b0558b99dca15076dc5..c6f57ccb5d0a15e72ef36ea7b8a95fccaebce762:/wxPython/docs/CHANGES.txt

diff --git a/wxPython/docs/CHANGES.txt b/wxPython/docs/CHANGES.txt
index 350aa5dbe5..30254e59c4 100644
--- a/wxPython/docs/CHANGES.txt
+++ b/wxPython/docs/CHANGES.txt
@@ -1,21 +1,34 @@
 Recent Changes for wxPython
 =====================================================================
 
-2.5.1.6
+2.5.2.0
 -------
 
 wx.ADJUST_MINSIZE is now the default behaviour for window items in
 sizers.  This means that the item's GetMinSize and/or GetBestSize will
 be called when calculating layout and the return value from that will
-be used for the minimum size.  The wx.FIXED_MINSIZE flag was added
-that will cause the sizer to *not* call window methods to determine
-the new best size, instead the minsize that the window had when added
-to the sizer (or the size the window was created with) will always be
-used.  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.  You can set the window's minimal size (via
-SetSizeHints) to manually control wha tthe sizer will use when
-calculating layout.
+be used for the minimum size used by the sizer.  The wx.FIXED_MINSIZE
+flag was added that will cause the sizer to use the old behaviour in
+that it will *not* call the window's methods to determine the new best
+size, instead the minsize that the window had when added to the sizer
+(or the size the window was created with) will always be used.  
+
+Related to the above, when controls and some other window types are
+created either the size passed to the constructor, or their "best
+size" if an explicit size was not passed in, is set as the window's
+minimal size.  For non top-level windows that hasn't meant much in the
+past, but now the sizers are sensitive to the window's minimal size.
+The key point to understand here is that it is no longer the window's
+size it has when added to the sizer that matters, but its minimal
+size.  So you might have some issues to iron out if you create a
+control without a size and then set its size to something before
+adding it to the sizer.  Since it's minimal size is probably not the
+size you set then the sizer will appear to be misbehaving.  The fix is
+to either set the size when calling the window's constructor, or to
+reset the min size by calling SetSizeHints.  You can call SetSizeHints
+at anytime to change the minsize of a window, just call the sizer's
+Layout method to redistribute the controls as needed.
+
 
 Added new MaskedEditControl code from Will Sadkin.  The modules are
 now locaed in their own sub-package, wx.lib.masked.  Demos updated.
@@ -64,6 +77,11 @@ running on wxGTK to work around the fact that GTK requires the locale
 to be set to the system settings but Python depends on LC_NUMERIC
 remaining compatible with "C".
 
+Switched gizmos.TreeListCtrl to the newer version of the code from the
+wxCode project.
+
+
+
 
 
 2.5.1.5