Force the output window to display at the begining of the app

[wxWidgets.git] / wxPython / docs / MigrationGuide.txt

diff --git a/wxPython/docs/MigrationGuide.txt b/wxPython/docs/MigrationGuide.txt
index 70ee5f4a05345f9a78cb27391b73d624c7ab5e56..a0de5716229b73d9cf035de5b223f4256f065e54 100644 (file)
--- a/wxPython/docs/MigrationGuide.txt
+++ b/wxPython/docs/MigrationGuide.txt
@@ -424,7 +424,7 @@ be used from XRC.
 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.2.x]**
-AddWindow, AddSize, AddSpacer and etc. will now issue a
+AddWindow, AddSizer, AddSpacer and etc. will now issue a
 DeprecationWarning. 
 
 **[Changed in 2.5.2.x]** The Sizers have had some fundamental internal
@@ -698,10 +698,11 @@ there seems to be less and less interest in maintaining the C++
 version.  
 
 There are only a few known compatibility issues at this time.  First
-is the location of OGL.  The deprecated version is located in the
-wx.ogl module, and the new version is in the wx.lib.ogl package.  So
-this just means that to start using the new version you need to adjust
-your imports.  So if your code currently has something like this::
+is that the ogl.DrawnShape has not been reimplemented yet.  Next is the
+location of OGL.  The deprecated version is located in the wx.ogl
+module, and the new version is in the wx.lib.ogl package.  So this
+just means that to start using the new version you need to adjust your
+imports.  So if your code currently has something like this::
 
      import wx
      import wx.ogl as ogl
@@ -863,3 +864,21 @@ for changes in capabilities, usage, etc.
 and will raise a DeprecationWarning if used.  The main wx.Mask
 constructor has been modified to be compatible with wx.MaskColour so
 you should use it instead.
+
+**[Changed in 2.5.2.x]** In wx.TextCtrls that have the
+wx.TE_PROCESS_TAB style the TAB key will be treated like an ordinary
+character and will not cause any tab traversal navigation at all.  If
+you use this style but would still like to have the normal tab
+traversal take place then you should send your own
+wx.NavigationKeyEvent from the wx.EVT_KEY_DOWN handler.  There is a
+new Navigate method in the wx.Window class to help send the event and
+it is used something like this::
+
+       flags = wx.NavigationKeyEvent.IsForward
+       if event.ShiftDown():
+           flags = wx.NavigationKeyEvent.IsBackward
+       if event.ControlDown():
+           flags |= wx.NavigationKeyEvent.WinChange
+       self.Navigate(flags)
+
+