X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/9ec83f8da72081593c79326b30a14e40003c1945..66c033b4a6ee95a2392b7f3c5a629256b661c456:/wxPython/docs/MigrationGuide.txt diff --git a/wxPython/docs/MigrationGuide.txt b/wxPython/docs/MigrationGuide.txt index eea0562cc0..9f14102f5c 100644 --- a/wxPython/docs/MigrationGuide.txt +++ b/wxPython/docs/MigrationGuide.txt @@ -347,13 +347,17 @@ Then you can just simplify it like this:: dc.DrawRectangle(p, s) Now before you start yelling and screaming at me for breaking all your -code, take note that up above I said, "...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. +code, take note that up above I said, "...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. Unfortunately there +is one exception to this behaviour. If a DC is returned from a +function or method then an instance of the new class (with the new +methods described above) will be returned instead of the compatibility +class. If/When the old wxPython.wx namespace is removed then these +compatibility classes will be removed too so you should plan on +migrating to the new namespace and new DC Draw methods before that +time. @@ -432,6 +436,11 @@ 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 wx.Size or a 2-integer sequence instead of separate width and height parameters. +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.) The wx.GridBagSizer class (very similar to the RowColSizer in the library) has been added to C++ and wrapped for wxPython. It can also @@ -441,6 +450,17 @@ 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. +**[Changed in 2.5.1.6]** 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. The +wx.FIXED_MINSIZE flag was added that will cause the sizer to *not* +call window 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. When a window is added +to a sizer it's initial size, if any, is set as the window's minimal +size using SetSizeHints if there isn't already a minimal size. + PlatformInfo ------------ @@ -578,8 +598,8 @@ provided by the makers of the ActiveX control that you are using. -Other Stuff ------------ +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 @@ -588,11 +608,52 @@ later into the main namespace via Python code. 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 shoudl reall be using +the objects in these modules 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. @@ -600,6 +661,14 @@ Similarly, the wxSystemSettings backwards compatibiility aliases for 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 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 @@ -648,3 +717,8 @@ 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.1.6]** 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. +