wx.InitAllImageHandlers is now an empty function that does nothing but

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

diff --git a/wxPython/docs/CHANGES.txt b/wxPython/docs/CHANGES.txt
index dcdf99190b61564bbb077f8cfdd584534dc69c8c..57dcb784919881a38a6f1a2f6388f0956faa424d 100644 (file)
--- a/wxPython/docs/CHANGES.txt
+++ b/wxPython/docs/CHANGES.txt
@@ -5,21 +5,50 @@ Recent Changes for wxPython
 -------
 
 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.
+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.
+
+Deprecated the wx.iewin module.
+
+Deprecated the wx.Sizer.AddWindow, AddSizer, AddSpacer methods as well
+as their Insert* and Prepend* counterparts.
+
+Added a generic StaticBitmap class in wx.lib.statbmp for the same
+reasons that stattext was created, so it could be mouse sensitive on
+all platforms like normal windows.  Also updated stattext.py and
+buttons.py to handle attribute (font & colour) defaults and
+inheritance the new way.  If you have custom controls of your own you
+should review stattxt.py or one of the others to see how it is to be
+done.
+
+wx.InitAllImageHandlers is now an empty function that does nothing but
+exist for backwards compatibility.  The C++ version is now called
+automatically when wxPython is initialized.  Since all the handlers
+are included in the wxWidgets shared library anyway, this imposes only
+a very small amount of overhead and removes several unneccessary
+problems.
+
 
 
 
@@ -76,7 +105,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