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 +%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 @@ -326,7 +326,7 @@ headers in an i_files sibdirectory. It should be enough to pass a 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.
+scripts using import wx.build.config.You no longer need to call wxClassInfo::CleanUpClasses() and wxClassInfo::InitializeClasses() in your extensions or when embedding wxPython.
@@ -359,8 +359,8 @@ class MyDialog(wx.Dialog):The hack allowing the old "option" keyword parameter has been removed. If you use keyword args with wx.Sizer 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.)
+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 wx.Size or a 2-integer sequence instead of separate width and height parameters. This was optionally allowed in 2.4, but now it is required. This @@ -391,41 +391,41 @@ First a bit about how things used to work:
to be its minimal size, and that size would always be used by default when calculating layout size and positions, and the sizer itself would keep track of that minimal size. -The main thrust of the new Sizer changes was to make behavior like -wx.ADJUST_MINSIZE be the default, and also to push the tracking of +wx.ADJUST_MINSIZE be the default, and also to push the tracking of the minimal size to the window itself (since it knows its own needs) instead of having the sizer take care of it. Consequently these changes were made:
@@ -441,34 +441,34 @@ but now the sizer will use the default size as the minimum rather than the size set later. It is an easy fix though, just move the specification of the size to the constructor (assuming that SomeWidget will set its minsize there like the rest of the controls do) or call -SetMinSize instead of SetSize. +SetMinSize instead of SetSize.-
- The wx.FIXED_MINSIZE flag was added to allow for the old +
- The wx.FIXED_MINSIZE flag was added to allow for the old behavior. When this flag is used the size a window has when added to the sizer will be treated as its minimal size and it will not be readjusted on each layout.
-- The min size stored in wx.Window and settable with -SetSizeHints or SetMinSize will by default be used by +
- The min size stored in wx.Window and settable with +SetSizeHints or SetMinSize will by default be used by the sizer (if it was set) as the minimal size of the sizer item. If the min size was not set (or was only partially set) then the window's best size is fetched and it is used instead of (or -blended with) the min size. wx.Window.GetBestFittingSize +blended with) the min size. wx.Window.GetBestFittingSize was added to facilitate getting the size to be used by the sizers.
- The best size of a window is cached so it doesn't need to -recaculated on every layout. wx.Window.InvalidateBestSize +recaculated on every layout. wx.Window.InvalidateBestSize was added and should be called (usually just internally in control methods) whenever something is done that would make the best size change.
- All wxControls were changed to set the minsize to what is passed to the constructor or Create method, and also to set the real size of the control to the blending of the min size and best -size. wx.Window.SetBestFittingSize was added to help with +size. wx.Window.SetBestFittingSize was added to help with this, although most controls don't need to call it directly -because it is called indirectly via the SetInitialSize +because it is called indirectly via the SetInitialSize called in the base classes.
In order to fit well with this new scheme of things, all wxControls or custom controls should do the following things. (Depending on how they are used you may also want to do the same thing for non-control custom windows.)
-
Either override or inherit a meaningful DoGetBestSize method +
Either override or inherit a meaningful DoGetBestSize method that calculates whatever size is "best" for the control. Once that size is calculated then there should normally be a call to -CacheBestSize to save it for later use, unless for some +CacheBestSize to save it for later use, unless for some reason you want the best size to be recalculated on every layout.
-Note: In order to successfully override DoGetBestSize in -Python the class needs to be derived from wx.PyWindow, -wx.PyControl, or etc. If your class instead derives from +
Note: In order to successfully override DoGetBestSize in +Python the class needs to be derived from wx.PyWindow, +wx.PyControl, or etc. If your class instead derives from one of the standard wx classes then just be sure that the min size gets explicitly set to what would have been the best size and things should work properly in almost all situations.
Any method that changes the attributes of the control such that -the best size will change should call InvalidateBestSize so +the best size will change should call InvalidateBestSize so it will be recalculated the next time it is needed.
The control's constructor and/or Create method should ensure that the minsize is set to the size passed in, and that the control is sized to a blending of the min size and best size. -This can be done by calling SetBestFittingSize.
+This can be done by calling SetBestFittingSize.