============================
This document will help explain some of the major changes in wxPython
-2.5 and let you know what you need to do to adapt your programs to
-those changes. Be sure to also check in the CHANGES.txt file like
-usual to see info about the not so major changes and other things that
-have been added to wxPython.
+2.5 since the 2.4 series and let you know what you need to do to adapt
+your programs to those changes. Be sure to also check in the CHANGES_
+file like usual to see info about the not so major changes and other
+things that have been added to wxPython.
+
+.. _CHANGES: CHANGES.html
wxName Change
The **wxWindows** project and library is now known as
**wxWidgets**. Please see here_ for more details.
-.. _here: http://www.wxwindows.org/name.htm
+.. _here: http://www.wxwidgets.org/name.htm
This won't really affect wxPython all that much, other than the fact
-that the wxwindows.org domain name will be changing to wxwidgets.org,
-so mail list, CVS, and etc. addresses will be changing. We're going
+that the wxwindows.org domain name has changed to wxwidgets.org,
+so mail list, CVS, and etc. addresses have also changed. We're going
to try and smooth the transition as much as possible, but I wanted you
all to be aware of this change if you run into any issues.
distribution.) This has some far reaching ramifications:
All classes derive from object and so all are now "new-style
- classes"
+ classes." This also allows you to use mixin classes that are
+ new-style and to use properties, staticmethod, etc.
Public data members of the C++ classes are wrapped as Python
- properties using property() instead of using __getattr__/__setattr__
- like before. Normally you shouldn't notice any difference, but if
- you were previously doing something with __getattr__/__setattr__
- in derived classes then you may have to adjust things.
-
- Static C++ methods are wrapped using the staticmethod()
- feature of Python and so are accessible as ClassName.MethodName
- as expected. They are still available as top level functions
+ properties using property() instead of using
+ __getattr__/__setattr__ hacks like before. Normally you shouldn't
+ notice any difference, but if you were previously doing something
+ with __getattr__/__setattr__ in derived classes then you may have
+ to adjust things.
+
+ Static C++ methods are wrapped using the staticmethod() feature of
+ Python and so are accessible as ClassName.MethodName as expected.
+ They are still also available as top level functions named like
ClassName_MethodName as before.
The relationship between the wxFoo and wxFooPtr classes have
changed for the better. Specifically, all instances that you see
- will be wxFoo even if they are created internally using wxFooPtr,
- because wxFooPtr.__init__ will change the instance's __class__ as
+ will be wx.Foo even if they are created internally using wx.FooPtr,
+ because wx.FooPtr.__init__ will change the instance's __class__ as
part of the initialization. If you have any code that checks
- class type using something like isinstance(obj, wxFooPtr) you will
- need to change it to isinstance(obj, wxFoo).
+ class type using something like isinstance(obj, wx.FooPtr) you will
+ need to change it to isinstance(obj, wx.Foo).
All of the EVT_* functions are now instances of the wx.PyEventBinder
class. They have a __call__ method so they can still be used as
functions like before, but making them instances adds some
-flexibility.
+flexibility that I expect to take advantave of in the future.
wx.EvtHandler (the base class for wx.Window) now has a Bind method that
makes binding events to windows a little easier. Here is its
If you create your own custom event types and EVT_* functions, and you
want to be able to use them with the Bind method above then you should
-change your EVT_* to be an instance of wxPyEventBinder instead of a
-function. If you used to have something like this::
+change your EVT_* to be an instance of wx.PyEventBinder instead of a
+function. For example, if you used to have something like this::
myCustomEventType = wxNewEventType()
def EVT_MY_CUSTOM_EVENT(win, id, func):
The second parameter is an integer in [0, 1, 2] that specifies the
number of IDs that are needed to be passed to Connect.
+**[Changed in 2.5.2.0]** There is also an Unbind method added to
+wx.EvtHandler that can be used to disconenct event handlers. It looks
+like this::
+
+ def Unbind(self, event, source=None, id=wx.ID_ANY, id2=wx.ID_ANY):
+ """
+ Disconencts the event handler binding for event from self.
+ Returns True if successful.
+ """
2.4, the compatibility modules are generated at build time and contain
assignment statements like this::
- wxWindow = wx.core.Window
+ wxWindow = wx._core.Window
-Don't let the "core" in the name bother you. That and some other
+Don't let the "_core" in the name bother you. That and some other
modules are implementation details, and everything that was in the
wxPython.wx module before will still be in the wx package namespace
-after this change. So from your code you would use it as wx.Window.
+after this change. So from your code you would use it as wx.Window or
+wxWindow if you import from the wxPython.wx module.
A few notes about how all of this was accomplished might be
interesting... SWIG is now run twice for each module that it is
New wx.DC Methods
-----------------
-Many of the Draw methods of wx.DC have alternate forms in C++ that take
-wxPoint or wxSize parameters (let's call these *Type A*) instead of
-the individual x, y, width, height, etc. parameters (and we'll call
-these *Type B*). In the rest of the library I normally made the *Type
-A* forms of the methods be the default method with the "normal" name,
-and had renamed the *Type B* forms of the methods to some similar
-name. For example in wx.Window we have these Python methods::
-
- SetSize(size) # Type A
- SetSizeWH(width, height) # Type B
-
-
-For various reasons the new *Type A* methods in wx.DC were never added
-and the existing *Type B* methods were never renamed. Now that lots
-of other things are also changing in wxPython it has been decided that
-it is a good time to also do the method renaming in wx.DC too in order
-to be consistent with the rest of the library. The methods in wx.DC
-that are affected are listed here::
-
- FloodFillXY(x, y, colour, style = wx.FLOOD_SURFACE)
- FloodFill(point, colour, style = wx.FLOOD_SURFACE)
-
- GetPixelXY(x, y)
- GetPixel(point)
+**[Changed in 2.5.2.0]** In wxPython 2.5.1.5 there was a new
+implementation of the wx.DC Draw and other methods that broke
+backwards compatibility in the name of consistency. That change has
+been reverted and the wx.DC Draw methods with 2.4 compatible
+signatures have been restored. In addition a new set of methods have
+been added that take wx.Point and/or wx.Size parameters instead of
+separate integer parameters. The Draw and etc. methods now available
+in the wx.DC class are::
- DrawLineXY(x1, y1, x2, y2)
- DrawLine(point1, point2)
- CrossHairXY(x, y)
- CrossHair(point)
+ FloodFill(self, x, y, colour, style = wx.FLOOD_SURFACE)
+ FoodFillPoint(self, pt, colour, style = wx.FLOOD_SURFACE)
- DrawArcXY(x1, y1, x2, y2, xc, yc)
- DrawArc(point1, point2, center)
-
- DrawCheckMarkXY(x, y, width, height)
- DrawCheckMark(rect)
-
- DrawEllipticArcXY(x, y, w, h, start_angle, end_angle)
- DrawEllipticArc(point, size, start_angle, end_angle)
-
- DrawPointXY(x, y)
- DrawPoint(point)
-
- DrawRectangleXY(x, y, width, height)
- DrawRectangle(point, size)
- DrawRectangleRect(rect)
+ GetPixel(self, x,y)
+ GetPixelPoint(self, pt)
+
+ DrawLine(self, x1, y1, x2, y2)
+ DrawLinePoint(self, pt1, pt2)
- DrawRoundedRectangleXY(x, y, width, height, radius)
- DrawRoundedRectangle(point, size, radius)
- DrawRoundedRectangleRect(rect, radius)
+ CrossHair(self, x, y)
+ CrossHairPoint(self, pt)
- DrawCircleXY(x, y, radius)
- DrawCircle(point, radius)
+ DrawArc(self, x1, y1, x2, y2, xc, yc)
+ DrawArcPoint(self, pt1, pt2, centre)
- DrawEllipseXY(x, y, width, height)
- DrawEllipse(point, size)
- DrawEllipseRect(rect)
+ DrawCheckMark(self, x, y, width, height)
+ DrawCheckMarkRect(self, rect)
- DrawIconXY(icon, x, y)
- DrawIcon(icon, point)
+ DrawEllipticArc(self, x, y, w, h, sa, ea)
+ DrawEllipticArcPointSize(self, pt, sz, sa, ea)
- DrawBitmapXY(bmp, x, y, useMask = FALSE)
- DrawBitmap(bmp, point, useMask = FALSE)
+ DrawPoint(self, x, y)
+ DrawPointPoint(self, pt)
- DrawTextXY(text, x, y)
- DrawText(text, point)
+ DrawRectangle(self, x, y, width, height)
+ DrawRectangleRect(self, rect)
+ DrawRectanglePointSize(self, pt, sz)
- DrawRotatedTextXY(text, x, y, angle)
- DrawRotatedText(text, point, angle)
+ DrawRoundedRectangle(self, x, y, width, height, radius)
+ DrawRoundedRectangleRect(self, r, radius)
+ DrawRoundedRectanglePointSize(self, pt, sz, radius)
-
- BlitXY(xdest, ydest, width, height, sourceDC, xsrc, ysrc,
- rop = wxCOPY, useMask = FALSE, xsrcMask = -1, ysrcMask = -1)
- Blit(destPt, size, sourceDC, srcPt,
- rop = wxCOPY, useMask = FALSE, srcPtMask = wx.DefaultPosition)
+ DrawCircle(self, x, y, radius)
+ DrawCirclePoint(self, pt, radius)
- SetClippingRegionXY(x, y, width, height)
- SetClippingRegion(point, size)
- SetClippingRect(rect)
- SetClippingRegionAsRegion(region);
+ DrawEllipse(self, x, y, width, height)
+ DrawEllipseRect(self, rect)
+ DrawEllipsePointSize(self, pt, sz)
-
-If you have code that draws on a DC and you are using the new wx
-namespace then you **will** get errors because of these changes, but
-it should be easy to fix the code. You can either change the name of
-the *Type B* method called to the names shown above, or just add
-parentheses around the parameters as needed to turn them into tuples
-and let the SWIG typemaps turn them into the wx.Point or wx.Size
-object that is expected. Then you will be calling the new *Type A*
-method. For example, if you had this code before::
+ DrawIcon(self, icon, x, y)
+ DrawIconPoint(self, icon, pt)
- dc.DrawRectangle(x, y, width, height)
+ DrawBitmap(self, bmp, x, y, useMask = False)
+ DrawBitmapPoint(self, bmp, pt, useMask = False)
-You could either continue to use the *Type B* method bu changing the
-name to DrawRectabgleXY, or just change it to the new *Type A* by
-adding some parentheses like this::
+ DrawText(self, text, x, y)
+ DrawTextPoint(self, text, pt)
- dc.DrawRectangle((x, y), (width, height))
+ DrawRotatedText(self, text, x, y, angle)
+ DrawRotatedTextPoint(self, text, pt, angle)
-Or if you were already using a point and size::
+ bool Blit(self, xdest, ydest, width, height, sourceDC, xsrc, ysrc,
+ rop = wx.COPY, useMask = False, xsrcMask = -1, ysrcMask = -1)
+ BlitPointSize(self, destPt, sz, sourceDC, srcPt, rop = wx.COPY,
+ useMask = False, srcPtMask = wxDefaultPosition)
- dc.DrawRectangle(p.x, p.y, s.width, s.height)
-Then you can just simplify it like this::
+ SetClippingRegion(self, x, y, width, height)
+ SetClippingRegionPointSize(self, pt, sz)
+ SetClippingRegionAsRegion(self, region)
+ SetClippingRect(self, rect)
- dc.DrawRectangle(p, s)
-Now before you start yelling and screaming at me for breaking all your
-code, take note that I said above "...using the new wx namespace..."
-That's because if you are still importing from wxPython.wx then there
-are some classes defined there with Draw and etc. methods that have
-2.4 compatible signatures. However if/when the old wxPython.wx
-namespace is removed then these classes will be removed too so you
-should plan on migrating to the new namespace and new DC Draw methods
-before that time.
the contribs (gizmos, stc, xrc, etc.) rather than building local
copies of them. If you build your own copies of wxPython please be
aware that you now need to also build the ogl, stc, xrc, and gizmos
-libraries in addition to the main wx lib. [[TODO: update the
-BUILD.*.txt files too!]]
+libraries in addition to the main wx lib.
The wxPython.h and other header files are now in
-.../wxPython/include/wx/wxPython instead of in wxPython/src. You should
-include it via the "wx/wxPython/wxPython.h" path and add
-.../wxPython/include to your list of include paths. [[TODO: Install
-these headers on Linux...]]
+.../wxPython/include/wx/wxPython instead of in wxPython/src. You
+should include it via the "wx/wxPython/wxPython.h" path and add
+.../wxPython/include to your list of include paths. On OSX and
+unix-like systems the wxPython headers are installed to the same place
+that the wxWidgets headers are installed, so if you are building
+wxPython compatible extensions on those platforms then your include
+path should already be set properly.
+
+If you are also using SWIG for your extension then you'll need to
+adapt how the wxPython .i files are imported into your .i files. See
+the wxPython sources for examples. Your modules will need to at least
+``%import core.i``, and possibly others if you need the definition of
+other classes. Since you will need them to build your modules using
+SWIG, the main wxPython .i files are also installed with the wxPython
+headers in an i_files sibdirectory. It should be enough to pass a
+-I/pathname on the command line for SWIG to find the files.
+
+The bulk of wxPython's setup.py has been moved to another module,
+wx/build/config.py. This module will be installed as part of wxPython
+so 3rd party modules that wish to use the same setup/configuration
+code can do so simply by importing this module from their own setup.py
+scripts using ``import wx.build.config``.
You no longer need to call wxClassInfo::CleanUpClasses() and
wxClassInfo::InitializeClasses() in your extensions or when embedding
wxPython.
+The usage of wxPyBeginAllowThreads and wxPyEndAllowThreads has changed
+slightly. wxPyBeginAllowThreads now returns a boolean value that must
+be passed to the coresponding wxPyEndAllowThreads function call. This
+is to help do the RightThing when calls to these two functions are
+nested, or if calls to external code in other extension modules that
+are wrapped in the standard Py_(BEGIN|END)_ALLOW_THERADS may result in
+wx event handlers being called (such as during the call to
+os.startfile.)
------
The hack allowing the old "option" keyword parameter has been removed.
-If you use keyworkd args with wxSizer Add, Insert, or Prepend methods
-then you will need to use the "proportion" name instead of "option".
+If you use keyword args with w.xSizer Add, Insert, or Prepend methods
+then you will need to use the ``proportion`` name instead of
+``option``. (The ``proportion`` keyword was also allowed in 2.4.2.4.)
-When adding a spacer to a sizer you now need to use a wxSize or a
+When adding a spacer to a sizer you now need to use a wx.Size or a
2-integer sequence instead of separate width and height parameters.
-
-The wxGridBagSizer class (very similar to the RowColSizer in the
+This was optionally allowed in 2.4, but now it is required. This
+allows for more consistency in how you add the various types of items
+to a sizer. The first parameter defines the item (instead of the
+possibily first two, depending on if you are doing a spacer or not,)
+and that item can either be a window, a sizer or a spacer (which can
+be a sequence or a wx.Size.) Removing the option for separate width
+and height parameters greatly simplified the wrapper code.
+
+The wx.GridBagSizer class (very similar to the RowColSizer in the
library) has been added to C++ and wrapped for wxPython. It can also
be used from XRC.
You should not use AddWindow, AddSizer, AddSpacer (and similar for
Insert, Prepend, and etc.) methods any longer. Just use Add and the
-wrappers will figure out what to do.
+wrappers will figure out what to do. **[Changed in 2.5.2.0]**
+AddWindow, AddSize, AddSpacer and etc. will now issue a
+DeprecationWarning.
+
+**[Changed in 2.5.2.0]** 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.
+
+Related to the above, when controls and some other window types are
+created either the size passed to the constructor, or their "best
+size" if an explicit size was not passed in, is set as the window's
+minimal size. For non top-level windows that hasn't meant much in the
+past, but now the sizers are sensitive to the window's minimal size.
+The key point to understand here is that it is no longer the window's
+size it has when added to the sizer that matters, but its minimal
+size. So you might have some issues to iron out if you create a
+control without a size and then set its size to something before
+adding it to the sizer. Since it's minimal size is probably not the
+size you set then the sizer will appear to be misbehaving. The fix is
+to either set the size when calling the window's constructor, or to
+reset the min size by calling SetSizeHints. You can call SetSizeHints
+at anytime to change the minsize of a window, just call the sizer's
+Layout method to redistribute the controls as needed.
+
PlatformInfo
-Other Stuff
------------
+ActiveX
+-------
+
+Lindsay Mathieson's newest wxActiveX_ class has been wrapped into a new
+extension module called wx.activex. It is very generic and dynamic
+and should allow hosting of arbitray ActiveX controls within your
+wxPython apps. So far I've tested it with IE, PDF, and Flash
+controls, (and there are new samples in the demo and also library
+modules supporting these.)
+
+.. _wxActiveX: http://members.optusnet.com.au/~blackpaw1/wxactivex.html
+
+The new wx.activex module contains a bunch of code, but the most
+important things to look at are ActiveXWindow and ActiveXEvent.
+ActiveXWindow derives from wxWindow and the constructor accepts a
+CLSID for the ActiveX Control that should be created. (There is also
+a CLSID class that can convert from a progID or a CLSID String.) The
+ActiveXWindow class simply adds methods that allow you to query some
+of the TypeInfo exposed by the ActiveX object, and also to get/set
+properties or call methods by name. The Python implementation
+automatically handles converting parameters and return values to/from
+the types expected by the ActiveX code as specified by the TypeInfo,
+(just bool, integers, floating point, strings and None/Empty so far,
+but more can be handled later.)
+
+That's pretty much all there is to the class, as I mentioned before it
+is very generic and dynamic. Very little is hard-coded and everything
+that is done with the actual ActiveX control is done at runtime and
+referenced by property or method name. Since Python is such a dynamic
+language this is a very good match. I thought for a while about doing
+some Python black-magic and making the specific methods/properties of
+the actual ActiveX control "appear" at runtime, but then decided that
+it would be better and more understandable to do it via subclassing.
+So there is a utility class in wx.activex that given an existing
+ActiveXWindow instance can generate a .py module containing a derived
+class with real methods and properties that do the Right Thing to
+reflect those calls to the real ActiveX control. There is also a
+script/tool module named genaxmodule that given a CLSID or progID and
+a class name, will generate the module for you. There are a few
+examples of the output of this tool in the wx.lib package, see
+iewin.py, pdfwin.py and flashwin.py.
+
+Currently the genaxmodule tool will tweak some of the names it
+generates, but this can be controled if you would like to do it
+differently by deriving your own class from GernerateAXModule,
+overriding some methods and then using this class from a tool like
+genaxmodule. [TODO: make specifying a new class on genaxmodule's
+command-line possible.] The current default behavior is that any
+event names that start with "On" will have the "On" dropped, property
+names are converted to all lower case, and if any name is a Python
+keyword it will have an underscore appended to it. GernerateAXModule
+does it's best when generating the code in the new module, but it can
+only be as good as the TypeInfo data available from the ActiveX
+control so sometimes some tweaking will be needed. For example, the
+IE web browser control defines the Flags parameter of the Navigate2
+method as required, but MSDN says it is optional.
+
+It is intended that this new wx.activex module will replace both the
+older version of Lindsay's code available in iewin.IEHtmlWindow, and
+also the wx.lib.activexwraper module. Probably the biggest
+differences you'll ecounter in migrating activexwrapper-based code
+(besides events working better without causing deadlocks) is that
+events are no longer caught by overriding methods in your derived
+class. Instead ActiveXWindow uses the wx event system and you bind
+handlers for the ActiveX events exactly the same way you do for any wx
+event. There is just one extra step needed and that is creating an
+event ID from the ActiveX event name, and if you use the genaxmodule
+tool then this extra step will be handled for you there. For example,
+for the StatusTextChange event in the IE web browser control, this
+code is generated for you::
+
+ wxEVT_StatusTextChange = wx.activex.RegisterActiveXEvent('StatusTextChange')
+ EVT_StatusTextChange = wx.PyEventBinder(wxEVT_StatusTextChange, 1)
+
+and you would use it in your code like this::
+
+ self.Bind(iewin.EVT_StatusTextChange, self.UpdateStatusText, self.ie)
+
+When the event happens and your event handler function is called the
+event properties from the ActiveX control (if any) are converted to
+attributes of the event object passed to the handler. (Can you say
+'event' any more times in a single sentence? ;-) ) For example the
+StatusTextChange event will also send the text that should be put into
+the status line as an event parameter named "Text" and you can access
+it your handlers as an attribute of the event object like this::
+
+ def UpdateStatusText(self, evt):
+ self.SetStatusText(evt.Text)
+
+Usually these event object attributes should be considered read-only,
+but some will be defined by the TypeInfo as output parameters. In
+those cases if you modify the event object's attribute then that value
+will be returned to the ActiveX control. For example, to prevent a
+new window from being opened by the IE web browser control you can do
+this in the handler for the iewin.EVT_NewWindow2 event::
+
+ def OnNewWindow2(self, evt):
+ evt.Cancel = True
+
+So how do you know what methods, events and properties that an ActiveX
+control supports? There is a funciton in wx.activex named GetAXInfo
+that returns a printable summary of the TypeInfo from the ActiveX
+instance passed in. You can use this as an example of how to browse
+the TypeInfo provided, and there is also a copy of this function's
+output appended as a comment to the modules produced by the
+genaxmodule tool. Beyond that you'll need to consult the docs
+provided by the makers of the ActiveX control that you are using.
+
+
+
+OGL is dead! LONG LIVE OGL!
+---------------------------
+
+**[Changed in 2.5.2.0]**
+
+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.
+
+There are only a few known compatibility issues at this time. First
+is the location of OGL. The deprecated version is located in the
+wx.ogl module, and the new version is in the wx.lib.ogl package. So
+this just means that to start using the new version you need to adjust
+your imports. So if your code currently has something like this::
+
+ import wx
+ import wx.ogl as ogl
+
+Then just change it to this::
+
+ import wx
+ import wx.lib.ogl as ogl
+
+The other compatibility issue deals with removing a wart in the
+original API that was necessary in order to allow overloaded methods
+in derived classes to call the same method in the base class when
+using the old SWIG. Instead dedaling with the wart you can now just
+call the base class method like you woudl for any other Python class.
+For example, if you had to do something like this previously::
+
+ class MyDividedShape(ogl.DividedShape):
+ ...
+ def OnSizingEndDragLeft(self, pt, x, y, keys, attch):
+ self.base_OnSizingEndDragLeft(pt, x, y, keys, attch)
+ ...
+
+You will need to change it to be like this::
+
+ class MyDividedShape(ogl.DividedShape):
+ ...
+ def OnSizingEndDragLeft(self, pt, x, y, keys, attch):
+ ogl.DividedShape.OnSizingEndDragLeft(self, pt, x, y, keys, attch)
+ ...
+
+
+
+Obsolete Modules
+----------------
Instead of over a dozen separate extension modules linked together
into a single extension module, the "core" module is now just a few
Because of the above and also because of the way the new SWIG works,
the "internal" module names have changed, but you shouldn't have been
-using them anyway so it shouldn't bother you. ;-)
+using them anyway so it shouldn't bother you. ;-) In case you were
+erroneously using them in 2.4, here are the internal extension modules
+no longer exist:
+
+ * clip_dnd
+ * cmndlgs
+ * controls
+ * controls2
+ * events
+ * filesys
+ * fonts
+ * frames
+ * gdi
+ * image
+ * mdi
+ * misc
+ * misc2
+ * printfw
+ * sizers
+ * stattool
+ * streams
+ * utils
+ * windows
+ * windows2
+ * windows3
+
+They have been replaced by the following, but please remember that
+these are just "implementation details" and you should really be using
+the objects in these modules only via the wx or wxPython.wx packages:
+
+ * _core
+ * _gdi
+ * _windows
+ * _controls
+ * _misc
+
The help module no longer exists and the classes therein are now part
of the core module imported with wxPython.wx or the wx package.
+
+
+
+Other Stuff
+-----------
+
wxPyDefaultPosition and wxPyDefaultSize are gone. Use the
wxDefaultPosition and wxDefaultSize objects instead.
GetSystemColour, GetSystemFont and GetSystemMetric have also gone into
the bit-bucket. Use GetColour, GetFont and GetMetric instead.
+Use the Python True/False constants instead of the true, TRUE, false,
+FALSE that used to be provided with wxPython.
+
+Use None instead of the ancient and should have been removed a long
+time ago wx.NULL alias.
+
+wx.TreeCtrl.GetFirstChild no longer needs to be passed the cookie
+variable as the 2nd parameter. It still returns it though, for use
+with GetNextChild.
The wx.NO_FULL_REPAINT_ON_RESIZE style is now the default style for
all windows. The name still exists for compatibility, but it is set
The wxWave class has been renamed to wxSound, and now has a slightly
different API.
+
+wx.TaskbarIcon works on wxGTK-based platforms (for some window
+managers,) however you have to manage it a little bit more than you
+did before. Basically, the app will treat it like a top-level frame
+in that if the wx.TaskBarIcon still exists when all the frames are
+closed then the app will still not exit. You need to ensure that the
+wx.TaskBarIcon is destroyed when your last Frame is closed. For
+wxPython apps it is usually enough if your main frame object holds the
+only reference to the wx.TaskBarIcon, then when the frame is closed
+Python reference counting takes care of the rest.
+
+Before Python 2.3 it was possible to pass a floating point object as a
+parameter to a function that expected an integer, and the
+PyArg_ParseTuple family of functions would automatically convert to
+integer by truncating the fractional portion of the number. With
+Python 2.3 that behavior was deprecated and a deprecation warning is
+raised when you pass a floating point value, (for example, calling
+wx.DC.DrawLine with floats for the position and size,) and lots of
+developers using wxPython had to scramble to change their code to call
+int() before calling wxPython methods. Recent changes in SWIG have
+moved the conversion out of PyArg_ParseTuple to custom code that SWIG
+generates. Since the default conversion fragment was a little too
+strict and didn't generate a very meaningful exception when it failed,
+I decided to use a custom fragment instead, and it turned out that
+it's very easy to allow floats to be converted again just like they
+used to be. So, in a nutshell, any numeric type that can be
+converted to an integer is now legal to be passed to SWIG wrapped
+functions in wxPython for parameters that are expecting an integer.
+If the object is not already an integer then it will be asked to
+convert itself to one. A similar conversion fragment is in place for
+parameters that expect floating point values.
+
+**[Changed in 2.5.2.0]** The MaskedEditCtrl modules have been moved
+to their own sub-package, wx.lib.masked. See the docstrings and demo
+for changes in capabilities, usage, etc.
+
+**[Changed in 2.5.2.0]** wx.MaskColour constructor has been deprecated
+and will raise a DeprecationWarning if used. The main wx.Mask
+constructor has been modified to be compatible with wx.MaskColour so
+you should use it instead.
projects / wxWidgets.git / blobdiff