The wxWindows project and library is now known as +wxWidgets. Please see here for more details.
+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 +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.
+The import-startup-bootstrap process employed by wxPython was changed -such that wxWindows and the underlying gui toolkit are not +such that wxWidgets and the underlying gui toolkit are not initialized until the wx.App object is created (but before wx.App.OnInit is called.) This was required because of some changes that were made to the C++ wxApp class.
@@ -31,7 +41,7 @@ potential problems are that the C++ side of the "stock-objects" (wx.BLUE_PEN, wx.TheColourDatabase, etc.) are not initialized until the wx.App object is created, so you should not use them until after you have created your wx.App object. If you do then an exception will -be raised telling you that the C++ object has not bene initialized +be raised telling you that the C++ object has not been initialized yet.Also, you will probably not be able to do any kind of GUI or bitmap operation unless you first have created an app object, (even on @@ -100,10 +110,30 @@ def Bind(self, event, handler, source=None, id=wxID_ANY, id2=wxID_ANY):
self.Bind(wx.EVT_SIZE, self.OnSize) self.Bind(wx.EVT_BUTTON, self.OnButtonClick, theButton) -self.Bind(wx.EVT_MENU, self.OnExit, id=ID_EXIT) +self.Bind(wx.EVT_MENU, self.OnExit, id=wx.ID_EXIT) ++
The wx.Menu methods that add items to a wx.Menu have been modified +such that they return a reference to the wx.MenuItem that was created. +Additionally menu items and toolbar items have been modified to +automatically generate a new ID if -1 is given, similar to using -1 +with window classess. This means that you can create menu or toolbar +items and event bindings without having to predefine a unique menu ID, +although you still can use IDs just like before if you want. For +example, these are all equivallent other than their specific ID +values:
++1. + item = menu.Append(-1, "E&xit", "Terminate the App") + self.Bind(wx.EVT_MENU, self.OnExit, item) + +2. + item = menu.Append(wx.ID_EXIT, "E&xit", "Terminate the App") + self.Bind(wx.EVT_MENU, self.OnExit, item) + +3. + menu.Append(wx.ID_EXIT, "E&xit", "Terminate the App") + self.Bind(wx.EVT_MENU, self.OnExit, id=wx.ID_EXIT)-
I hope to be able to remove the need for using IDs even for menu -events too...
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 @@ -174,12 +204,9 @@ app.MainLoop()
You shouldn't need to migrate all your modules over to use the new package and names right away as there are modules in place that try to provide as much backwards compatibility of the names as possible. If -you rewrote the above sample using "from wxPython.wx import *", the +you rewrote the above sample using "from wxPython.wx import * ", the old wxNames, and the old style of event binding it will still work just fine.
-If you have code that draws on a DC 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:
+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:
dc.DrawRectangle(x, y, width, height)@@ -287,6 +315,14 @@ dc.DrawRectangle(p.x, p.y, s.width, s.height)
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 hack allowing the old "option" keyword parameter has been -removed. If you use keyworkd args with wxSizer Add, Insert, or -Prepend then you will need to use the "proportion" name instead of -"option".
+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".
When adding a spacer to a sizer you now need to use a wxSize or a 2-integer sequence instead of separate width and height parameters.
The wxGridBagSizer class (very similar to the RowColSizer in the @@ -336,18 +371,39 @@ be used from XRC.
Insert, Prepend, and etc.) methods any longer. Just use Add and the wrappers will figure out what to do.Added wx.PlatformInfo which is a tuple containing strings that +describe the platform and build options of wxPython. This lets you +know more about the build than just the __WXPORT__ value that +wx.Platform contains, such as if it is a GTK2 build. For example, +instead of:
++if wx.Platform == "__WXGTK__": + ... ++
you should do this:
++if "__WXGTK__" in wx.PlatformInfo: + ... ++
and you can specifically check for a wxGTK2 build by looking for +"gtk2" in wx.PlatformInfo. Unicode builds are also detectable this +way. If there are any other platform/toolkit/build flags that make +sense to add to this tuple please let me know.
+BTW, wx.Platform will probably be deprecated in the future.
+Instead of over a dozen separate extension modules linked together into a single extension module, the "core" module is now just a few extensions that are linked independently, and then merged together later into the main namespace via Python code.
-Because of the above, the "internal" module names have changed, but -you shouldn't have been using them anyway so it shouldn't bother -you. ;-)
-The wxPython.help module no longer exists and the classes therein are -now part of the core module imported with wxPython.wx or the wx -package.
+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. ;-)
+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.
wxPyDefaultPosition and wxPyDefaultSize are gone. Use the wxDefaultPosition and wxDefaultSize objects instead.
Similarly, the wxSystemSettings backwards compatibiility aliases for @@ -362,13 +418,22 @@ refreshed.
wxPyTypeCast has been removed. Since we've had the OOR (Original Object Return) for a couple years now there should be no need to use wxPyTypeCast at all.
+If you use the old wxPython package and wxPython.wx namespace then +there are compatibility aliases for much of the above items.
+The wxWave class has been renamed to wxSound, and now has a slightly +different API.
+Instead of a very small 20x20 the default window size is now a more +reasonable size, (currently 400x250 but that may change...) If you +don't specify a size, and the window/control class does not have any +definition of it's own "best size" (most controls do) then the new +default will be used. If you have code that accidentally depends on +the smaller size then things will look a bit odd. To work around this +just give those windows an explicit size when created.