Remove use of m_bestSize

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

diff --git a/wxPython/docs/CHANGES.txt b/wxPython/docs/CHANGES.txt
index 6c92a79c9c3a57a7b82f4f705834f319f75b378a..af1127d3e86a68efd46e2df9f91f59e27cc1a190 100644 (file)
--- a/wxPython/docs/CHANGES.txt
+++ b/wxPython/docs/CHANGES.txt
@@ -1,13 +1,35 @@
-CHANGES.txt for wxPython
+Recent Changes for wxPython

 =====================================================================
 
 =====================================================================
 

-2.5.1.2
+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.
+
+Added some convenience methods to wx.Bitmap: SetSize, GetSize, and
+wx.EmptyBitmap can be called with a wx.Size (or a 2-element sequence)
+object too.  Similar changes were done for wx.Image as well.
+
+
+
+
+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.)
 
 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
 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


@@ -107,6 +129,9 @@ MigrationGuide for more details on using the new module.
 
 .. _wxActiveX: http://members.optusnet.com.au/~blackpaw1/wxactivex.html
 
 
 .. _wxActiveX: http://members.optusnet.com.au/~blackpaw1/wxactivex.html
 

+Floats are allowed again as function parameters where ints are expected.
+
+

 
 
 2.4.2.4
 
 
 2.4.2.4