fixed bug in PS clipping (non-virtual SetClippingRegion was overloaded)

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

diff --git a/utils/wxPython/README.txt b/utils/wxPython/README.txt
index dfc8f4c81c233689fe53d952deb4be069a581ae0..d2b1fa6b0a714e4151f7e654b3cc49eeaf509604 100644 (file)
--- a/utils/wxPython/README.txt
+++ b/utils/wxPython/README.txt
@@ -45,10 +45,26 @@ Or you can send mail directly to the list using this address:
 
 ----------------------------------------------------------------------
 
 
 ----------------------------------------------------------------------
 

+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
 --------------------
 

+This release is NOT syncronized with a snapshot release of wxGTK or
+wxMSW.  For MSW this isn't much of a problem since you can get the
+binaries from the web site.  For other platforms you'll have to build
+wxGTK from CVS.  (See http://web.ukonline.co.uk/julian.smart/wxwin/cvs.htm)
+To get the same set of sources from CVS that I used, checkout using
+the wxPy-2-1-4 tag.
+
+Now back to what's new...
+

 Much more support for event-less callbacks and add-on modules.
 
 Created add-on module with wxOGL classes.
 Much more support for event-less callbacks and add-on modules.
 
 Created add-on module with wxOGL classes.


@@ -113,7 +129,7 @@ to use them.
 
 Added the wxValidator class, and created a class named wxPyValidator
 that should be used for the base class of any Python validators.  See
 
 Added the wxValidator class, and created a class named wxPyValidator
 that should be used for the base class of any Python validators.  See

-the demo for an example.  Please not that you MUST implement a Clone
+the demo for an example.  Please note that you MUST implement a Clone

 method in your validator classes because of the way some things work
 in the underlying C++ library.  I did not add wxTextValidator because
 of some issues of how it transfers data to and from a wxString, which
 method in your validator classes because of the way some things work
 in the underlying C++ library.  I did not add wxTextValidator because
 of some issues of how it transfers data to and from a wxString, which


@@ -129,7 +145,7 @@ object?  Well now you can leave it out or explicitly set it to a true
 value.  This value now controls what is to be done with sys.stdout and
 sys.stderr.  A false value leaves them alone, and a true value sets
 them to an instance of wxPyOnDemandOutputWindow.  (On windows the
 value.  This value now controls what is to be done with sys.stdout and
 sys.stderr.  A false value leaves them alone, and a true value sets
 them to an instance of wxPyOnDemandOutputWindow.  (On windows the

-default is true, on other platforms the default is false.)  This class
+default is true, on unix platforms the default is false.)  This class

 creates a frame containing a wxTextCtrl as soon as anything is written
 to sys.stdout or sys.stderr.  If you close the window it will come
 back again the next time something is written.  (You can call
 creates a frame containing a wxTextCtrl as soon as anything is written
 to sys.stdout or sys.stderr.  If you close the window it will come
 back again the next time something is written.  (You can call


@@ -153,6 +169,19 @@ wx.py for more details.  A few words of caution:  if you are running
 your app in a debugger, changing sys.stdout and sys.stderr is likely
 to really screw things up.
 
 your app in a debugger, changing sys.stdout and sys.stderr is likely
 to really screw things up.
 

+Added wxCaret.  Unfortunately it's author has still not documented it
+in the wxWindows docs...
+
+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
+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.  (Unfortunately there is currently
+a bug in wxGTK's wxFrame.SetToolBar so the FloatBar has some
+problems...)
+
+

 
 
 What's new in 2.1b3
 
 
 What's new in 2.1b3