| | 1 | <?xml version="1.0" encoding="iso-8859-1" ?> |
| | 2 | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> |
| | 3 | <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> |
| | 4 | <head> |
| | 5 | <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> |
| | 6 | <meta name="generator" content="Docutils 0.3.1: http://docutils.sourceforge.net/" /> |
| | 7 | <title>Recent Changes for wxPython</title> |
| | 8 | <link rel="stylesheet" href="default.css" type="text/css" /> |
| | 9 | </head> |
| | 10 | <body> |
| | 11 | <div class="document" id="recent-changes-for-wxpython"> |
| | 12 | <h1 class="title">Recent Changes for wxPython</h1> |
| | 13 | <div class="section" id="id1"> |
| | 14 | <h1><a name="id1">2.5.2.1</a></h1> |
| | 15 | <p>wx.ADJUST_MINSIZE is now the default behaviour for window items in |
| | 16 | sizers. This means that the item's GetMinSize and/or GetBestSize will |
| | 17 | be called when calculating layout and the return value from that will |
| | 18 | be used for the minimum size used by the sizer. The wx.FIXED_MINSIZE |
| | 19 | flag was added that will cause the sizer to use the old behaviour in |
| | 20 | that it will <em>not</em> call the window's methods to determine the new best |
| | 21 | size, instead the minsize that the window had when added to the sizer |
| | 22 | (or the size the window was created with) will always be used.</p> |
| | 23 | <p>Related to the above, when controls and some other window types are |
| | 24 | created either the size passed to the constructor, or their "best |
| | 25 | size" if an explicit size was not passed in, is set as the window's |
| | 26 | minimal size. For non top-level windows that hasn't meant much in the |
| | 27 | past, but now the sizers are sensitive to the window's minimal size. |
| | 28 | The key point to understand here is that it is no longer the window's |
| | 29 | size it has when added to the sizer that matters, but its minimal |
| | 30 | size. So you might have some issues to iron out if you create a |
| | 31 | control without a size and then set its size to something before |
| | 32 | adding it to the sizer. Since it's minimal size is probably not the |
| | 33 | size you set then the sizer will appear to be misbehaving. The fix is |
| | 34 | to either set the size when calling the window's constructor, or to |
| | 35 | reset the min size by calling SetSizeHints. You can call SetSizeHints |
| | 36 | at anytime to change the minsize of a window, just call the sizer's |
| | 37 | Layout method to redistribute the controls as needed.</p> |
| | 38 | <p>Added new MaskedEditControl code from Will Sadkin. The modules are |
| | 39 | now locaed in their own sub-package, wx.lib.masked. Demos updated.</p> |
| | 40 | <p>The changes that implemented the incompatible wx.DC methods in 2.5.1.5 |
| | 41 | have been reverted. The wx.DC methods are now compatible with the 2.4 |
| | 42 | implemetation. In addition a set of renamed methods have been added |
| | 43 | that take wx.Point and/or wx.Size objects instead of individual |
| | 44 | parameters.</p> |
| | 45 | <p>Added wx.lib.mixins.listctrl.TextEditMixin, a mixin class that allows |
| | 46 | all columns of a wx.ListCtrl in report mode to be edited.</p> |
| | 47 | <p>Deprecated the wx.iewin module.</p> |
| | 48 | <p>Deprecated the wx.Sizer.AddWindow, AddSizer, AddSpacer methods as well |
| | 49 | as their Insert* and Prepend* counterparts.</p> |
| | 50 | <p>Added a generic StaticBitmap class in wx.lib.statbmp for the same |
| | 51 | reasons that stattext was created, so it could be mouse sensitive on |
| | 52 | all platforms like normal windows. Also updated stattext.py and |
| | 53 | buttons.py to handle attribute (font & colour) defaults and |
| | 54 | inheritance the new way. If you have custom controls of your own you |
| | 55 | should review stattxt.py or one of the others to see how it is to be |
| | 56 | done.</p> |
| | 57 | <p>wx.InitAllImageHandlers is now an empty function that does nothing but |
| | 58 | exist for backwards compatibility. The C++ version is now called |
| | 59 | automatically when wxPython is initialized. Since all the handlers |
| | 60 | are included in the wxWidgets shared library anyway, this imposes only |
| | 61 | a very small amount of overhead and removes several unneccessary |
| | 62 | problems.</p> |
| | 63 | <p>Replaced wx/lib/pubsub.py with a version that uses weak references to |
| | 64 | track the subscribers, plus other fixes/additions. Thanks go to |
| | 65 | Oliver Schoenborn and Robb Shecter.</p> |
| | 66 | <p>wxGTK now uses gtk_init_check so wxPython can raise an exception if |
| | 67 | there is no DISPLAY available or other initializaion problem.</p> |
| | 68 | <p>wx.GetKeyState now has an implementation for wxGTK and is able to |
| | 69 | detect the up/down or toggle state of modifier and toggle keys.</p> |
| | 70 | <p>The LC_NUMERIC locale is now reset back to "C" (compatibility) when |
| | 71 | running on wxGTK to work around the fact that GTK requires the locale |
| | 72 | to be set to the system settings but Python depends on LC_NUMERIC |
| | 73 | remaining compatible with "C".</p> |
| | 74 | <p>Switched gizmos.TreeListCtrl to the newer version of the code from the |
| | 75 | wxCode project.</p> |
| | 76 | <p>OGL is dead! LONG LIVE OGL! (Oops, sorry. A bit of my dramatic side |
| | 77 | leaked out there...) The wx.ogl module has been deprecated in favor |
| | 78 | of the new Python port of the OGL library located at wx.lib.ogl |
| | 79 |
projects / wxWidgets.git / blame_incremental