X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/8feec28c876b20dd98f1c73c694493ab2973226f..0967b57b85518167b93f64ccecb5a1b5dc2b2c51:/wxPython/docs/CHANGES.txt diff --git a/wxPython/docs/CHANGES.txt b/wxPython/docs/CHANGES.txt index c6d4558de4..538c4627ae 100644 --- a/wxPython/docs/CHANGES.txt +++ b/wxPython/docs/CHANGES.txt @@ -1,9 +1,9 @@ Recent Changes for wxPython ===================================================================== -2.7.0.1 +2.7.1.1 ------- -* +* 18-Oct-2006 The following deprecated items have been removed: @@ -267,6 +267,65 @@ Renamed wx.FutureCall to wx.CallLater so it is named more like wx.CallAfter. wx.FutureCall is now an empty subclass of wx.CallLater for compatibility of older code. +Added the wx.lib.customtreectrl the from Andrea Gavana. + +Added ChangeSelection to wx.BookCtrl (the base class for wx.Notebook +and other book controls) that is the same as SetSelection but doesn't +send the change events. + +Added wx.TextCtrl.ChangeValue() which is the same as SetValue() but +doesn't send the text changed event. + +For consistency, all classes having an Ok() method now also have +IsOk(), use of the latter form is preferred although the former hasn't +been deprecated yet + +Added the wx.AboutBox() function and wx.AboutDialogInfo class. They +provide a way to show a standard About box for the application, which +will either be a native dialog or a generic one depending on what info +is provided and if it can all be shown with the native dialog. + +The code in the animate contrib has been moved into the code wxWidgets +library, and refactored a bit along the way. For wxPython it still +exists in the wx.animate module, but has basically been reduced to two +classes, wx.animate.Animation, and wx.animate.AnimationCtrl. You load +the animated GIF (and hopefully there will be other supported formats +in the near future) in the Animation object, and then give that to the +AnimatedCtrl for display. See the demo for an example. There is also +still a GIFAnimationCtrl class that provides some level of backwards +compatibility with the old implementation. + +wxMac: The compile option that turns on the use of CoreGraphics (a.k.a +Quartz) for wxDC is now turned on by default. This means that all +drawing via wxDC is done using the new APIs from apple, instead of the +old Quick Draw API. There are, however, a few places where Quartz and +wxDC don't fit together very well, mainly the lack of support for +logical drawing operations such as XOR, but there is work in progress +to provide other ways to do the same sort of thing that will work with +Quartz and also on the other platforms. + +The first parts of a new 2D drawing API has been added with the +wx.GraphicsPath and wx.GraphicsContext classes. They wrap GDI+ on +Windows, Cairo on wxGTK and CoreGraphics on OS X. They allow path-based +drawing with alpha-blending and anti-aliasing, and use a floating +point cooridnate system. Currently they can only target drawing to +windows, but other wx.DC backends are forthcoming. The APIs may +evolve a bit more before they are finalaized with the 2.8 release, but +there is enough there now to get a good feel for how things will work. +There is also a transitional wx.GCDC class that provides the wx.DC API +on top of wx.GraphicsContext. Docs and a demo are still MIA. + +Added a wx.AutoBufferedPaintDC that is a subclass of wx.PaintDC on +platforms that do double buffering by default, and a subclass of +wx.BufferedPaintDC on the platforms that don't. You can use this +class to help avoid the overhead of buffering when it is not +needed. There is also a wx.AutoBufferedPaintDCFactory function that +does a little more and actually tests if the window has +double-buffering enabled and then decides whether to return a +wx.PaintDC or wx.BufferedPaintDC. This uses the new +wx.Window.IsDoubleBuffered method. + +