-CHANGES.txt for wxPython
+Recent Changes for wxPython
=====================================================================
-2.5.1.1
+
+2.5.2.8
-------
-(See also the MigrationGuide.txt file for details about some of the
+Predominantly a bug-fix release.
+
+ * Fixed fatal error due to improper wrapping of wx.FSFile.
+
+ * Fixed return type of EditableListBox.GetListCtrl
+
+ * Give generic tree and list controls a DoGetBestSize so they play
+ nicer with sizers when there is no minimal size.
+
+ * Some tweaks in the demo and samples to correct layout, some
+ flicker problems, and namespace use.
+
+ * Add wx.Image.ConvertAlphaToMask
+
+ * Minor corrections in wx.lib.dialogs
+
+ * wx.FileHistory constructor now accepts the documented 2nd
+ parameter.
+
+ * Corrections for exceptions in the new ogl
+
+ * Fixed XRCed to not use reparenting of windows to implement caching
+ of property panels, since Reparent on wxMac is not implemented.
+
+ * Add support for wxTAB_TRAVERSAL to the XRC handler for
+ wxScrolledWindow.
+
+ * Add support for all wxListBox styles to the XRC handler for
+ wxCheckListBox.
+
+ * Fix for wx.Listbook.DeleteAllPages to really delete everything.
+
+ * wxGTK2 now supports alpha blended bitmap drawing
+
+ * Made wx.grid.Grid play nicer with sizers.
+
+ * etc.
+
+
+
+
+2.5.2.7
+-------
+
+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 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. Please
+see the Sizers section in the Migration Guide for more details.
+
+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.
+
+Replaced wx/lib/pubsub.py with a version that uses weak references to
+track the subscribers, plus other fixes/additions. Thanks go to
+Oliver Schoenborn and Robb Shecter.
+
+wxGTK now uses gtk_init_check so wxPython can raise an exception if
+there is no DISPLAY available or other initializaion problem.
+
+wx.GetKeyState now has an implementation for wxGTK and is able to
+detect the up/down or toggle state of modifier and toggle keys.
+
+The LC_NUMERIC locale is now reset back to "C" (compatibility) when
+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.
+
+OGL is dead! LONG LIVE OGL! (Oops, sorry. A bit of my dramatic side
+leaked out there...) The wx.ogl module has been deprecated in favor
+of the new Python port of the OGL library located at wx.lib.ogl
+contributed by Pierre Hjälm. This will hopefully greatly extend the
+life of OGL within wxPython by making it more easily maintainable and
+less prone to getting rusty as there seems to be less and less
+interest in maintaining the C++ version. At this point there are just
+a couple minor known compatibility differences, please see the
+MigrationGuide_ file for details.
+
+.. _MigrationGuide: MigrationGuide.html
+
+EVT_STC_POSCHANGED has been removed as it has been deprecated in
+Scintilla for several releases now.
+
+All the Window and GDI (pen, bitmap, etc.) class constructors and also
+many toplevel functions and static methods will now check that a
+wx.App object has already been created and will raise a
+wx.PyNoAppError exception if not.
+
+Added more default args as needed to allow most window types to be
+constructed with only the parent window arg. In some cases other args
+may be required for normal operation, but they can usually be set
+after construction.
+
+Removed the deprecated ErrorDialogs and PythonBitmaps modules. If you
+were using these in your apps then please join wxPython-dev and assist
+with a more modern reimplementation.
+
+Added a new version (0.8.3) of FloatCanvas from Chris Barker. It's now
+in a subpackage of wx.lib.
+
+It is now possible to change the tab traversal order of controls on a
+panel or dialog. For details see the new MoveAfterInTabOrder and
+MoveBeforeInTabOrder methods of wx.Window.
+
+Applied (and heavily modified) a patch from Eugene
+<svip123@fastmail.fm> that allows the sample modules in the demo to be
+edited and reloaded, all from within the demo. You can switch back
+and forth between the default and your edited version, and any errors
+ocurring upon the reload are reported on the Demo tab.
+
+Added a menu item in the demo that will open a PyShell window that has
+the app and demo frame preloaded in the namespace. This is another
+good way to explore and play with the objects in the currently running
+sample. For example, load the Button sample and then do the following
+in the PyShell::
+
+ >>> b = frame.demoPage.GetChildren()[0]
+ >>> for x in range(0, 500, 10):
+ ... b.Move((x, 50))
+ ... app.Yield(True)
+ ... wx.MilliSleep(10)
+
+
+
+
+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
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
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