X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/b7c75283f2144469e8fa6a24ca285b42fab69a6b..0bdcd2f50750d235bff2766f3d03d7228aa88dff:/wxPython/docs/CHANGES.txt

diff --git a/wxPython/docs/CHANGES.txt b/wxPython/docs/CHANGES.txt
index b1d028aced..564f883c82 100644
--- a/wxPython/docs/CHANGES.txt
+++ b/wxPython/docs/CHANGES.txt
@@ -1,13 +1,46 @@
-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 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.
+
+Added new MaskedEditControl code from Will Sadkin.  The modules are
+now locaed in their own sub-package, wx.lib.masked.  Demos updated.
+
+The changes that implemented the incompatible wx.DC methods in 2.5.1.5
+have been reverted.  The wx.DC methods are now compatible with the 2.4
+implemetation.  In addition a set of renamed methods have been added
+that take wx.Point and/or wx.Size objects instead of individual
+parameters. 
+
+Added wx.lib.mixins.listctrl.TextEditMixin, a mixin class that allows
+all columns of a wx.ListCtrl in report mode to be edited.
+
+
+
+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
@@ -51,7 +84,7 @@ installing them also on my main Mandrake 9.2 box.
 
 There are some big changes in the OS X disk image.  The actual
 Installer package now *only* installs the wxMac dynlibs, wxPython
-extension modules and Python pacakges, and also the command-line tool
+extension modules and Python packages, and also the command-line tool
 scripts. The remaining items (demo, samples, and application bundles
 for the Demo, PyCrust and XRCed) are now top-level items in the disk
 image (.dmg file) that users can just drag and drop to wherever they
@@ -96,18 +129,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