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 @@ -109,7 +119,8 @@ 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 ID values:
+example, these are all equivallent other than their specific ID +values:1. item = menu.Append(-1, "E&xit", "Terminate the App") @@ -360,6 +371,28 @@ 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 @@ -389,11 +422,18 @@ wxPyTypeCast at all.
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.