Made SetType public to match MSW.

[wxWidgets.git] / utils / wxPython / README.txt

diff --git a/utils/wxPython/README.txt b/utils/wxPython/README.txt
index c6a2290cdfb10b809bfbc9a52c7fb6afa2bb5df4..9e73f20ff3e15170ed0102db1ddd8fdd9c425300 100644 (file)
--- a/utils/wxPython/README.txt
+++ b/utils/wxPython/README.txt
@@ -45,6 +45,57 @@ Or you can send mail directly to the list using this address:
 
 ----------------------------------------------------------------------
 
 
 ----------------------------------------------------------------------
 

+What's new in 2.1.11
+--------------------
+wxImage.SetData now makes a copy of the image data before giving it to
+wxImage.  I mistakenly thought that wxImage would copy the data
+itself.
+
+Fixed wxMSW's notebook so the pages get their size set as they are
+being added.  This should remove the need for our
+wxNotebook.ResizeChildren hack.
+
+wxPanels now support AutoLayout, and wxNotebooks and wxSplitterWindows
+no longer tell their children to Layout() themselves.  This will
+probably only effect you if you have a wxWindow with AutoLayout inside
+a notebook or splitter.  If so, either change it to a wxPanel or add
+an EVT_SIZE handler that calls Layout().
+
+Fixed deadlock problem that happened when using threads.
+
+Added new HTML printing classes.
+
+Added wxWindow.GetHandle
+
+Apparently wxMouseEvent.Position has been depreciated in wxWindows as
+it is no longer available by default.  You can use GetPositionTuple
+(returning a tuple with x,y) instead, or GetPosition (returning a
+wxPoint.)
+
+Added wxPostEvent function that allows events to be posted and then
+processed later.  This is a thread-safe way to interact with the GUI
+thread from other threads.
+
+Added Clipboard and Drag-and-Drop classes.
+
+Added wxFontEnumerator.
+
+Many updates to wxMenu, wxMenuBar.
+
+wxPyEvent and wxPyCommandEvent derived classes now give you the actual
+Python object in the event handler.
+
+
+
+
+
+What's new in 2.1.5
+-------------------
+This is a quick bug-fix release to take care of a few nasties that
+crept in at the last minute before 2.1.4 was called done.  No new
+major features.
+
+

 
 What's new in 2.1.4
 --------------------
 
 What's new in 2.1.4
 --------------------


@@ -91,7 +142,7 @@ wxGTK.  Added them back in since the methods exist now.
 
 Wrapped the wxHtmlHelpController and related classes.
 
 
 Wrapped the wxHtmlHelpController and related classes.
 

-Wrapped the C++ versions of wxSizer and firends.  The Python-only
+Wrapped the C++ versions of wxSizer and friends.  The Python-only

 versions are still in the library, but depreciated.  (You will get a
 warning message if you try to use them, but the warning can be
 disabled.) The usage of the C++ versions is slightly different, and
 versions are still in the library, but depreciated.  (You will get a
 warning message if you try to use them, but the warning can be
 disabled.) The usage of the C++ versions is slightly different, and


@@ -167,10 +218,12 @@ in the wxWindows docs...
 
 Some new 3rd party contributions in wxPython.lib.  PyShell, in
 shell.py is an interesting implementaion of an interactive Python
 
 Some new 3rd party contributions in wxPython.lib.  PyShell, in
 shell.py is an interesting implementaion of an interactive Python

-shell in wxWindows.  floatbar.py has a class derived from wxTooBar
+shell in wxWindows.  floatbar.py has a class derived from wxToolBar

 that can sense mouse drags and then reparent itself into another
 frame. Moving the new frame close to where it came from puts the tool
 that can sense mouse drags and then reparent itself into another
 frame. Moving the new frame close to where it came from puts the tool

-bar back into the original parent.
+bar back into the original parent.  (Unfortunately there is currently
+a bug in wxGTK's wxFrame.SetToolBar so the FloatBar has some
+problems...)