wxUSE_STL/wxArrayString fixes.

[wxWidgets.git] / wxPython / docs / CHANGES.html

diff --git a/wxPython/docs/CHANGES.html b/wxPython/docs/CHANGES.html
index b2b2945859863cbd87c2e9a2ff8f2275cb145d19..4cf883dfae773075e0c5e432ca684b7796c09dc4 100644 (file)
--- a/wxPython/docs/CHANGES.html
+++ b/wxPython/docs/CHANGES.html
@@ -19,22 +19,8 @@ be used for the minimum size used by the sizer.  The wx.FIXED_MINSIZE
 flag was added that will cause the sizer to use the old behaviour in
 that it will <em>not</em> call the window's 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.</p>
-<p>Related to the above, when controls and some other window types are
-created either the size passed to the constructor, or their &quot;best
-size&quot; if an explicit size was not passed in, is set as the window's
-minimal size.  For non top-level windows that hasn't meant much in the
-past, but now the sizers are sensitive to the window's minimal size.
-The key point to understand here is that it is no longer the window's
-size it has when added to the sizer that matters, but its minimal
-size.  So you might have some issues to iron out if you create a
-control without a size and then set its size to something before
-adding it to the sizer.  Since it's minimal size is probably not the
-size you set then the sizer will appear to be misbehaving.  The fix is
-to either set the size when calling the window's constructor, or to
-reset the min size by calling SetSizeHints.  You can call SetSizeHints
-at anytime to change the minsize of a window, just call the sizer's
-Layout method to redistribute the controls as needed.</p>
+(or the size the window was created with) will always be used.  Please
+see the Sizers section in the Migration Guide for more details.</p>
 <p>Added new MaskedEditControl code from Will Sadkin.  The modules are
 now locaed in their own sub-package, wx.lib.masked.  Demos updated.</p>
 <p>The changes that implemented the incompatible wx.DC methods in 2.5.1.5
@@ -97,6 +83,9 @@ were using these in your apps then please join wxPython-dev and assist
 with a more modern reimplementation.</p>
 <p>Added a new version (0.8.3) of FloatCanvas from Chris Barker.  It's now
 in a subpackage of wx.lib.</p>
+<p>It is now possible to change the tab traversal order of controls on a
+panel or dialog.  For details see the new MoveAfterInTabOrder and
+MoveBeforeInTabOrder methods of wx.Window.</p>
 </div>
 <div class="section" id="id2">
 <h1><a name="id2">2.5.1.5</a></h1>