From 2ce9b1bfd310e61bbfb5ad1e568144fe9efc14f7 Mon Sep 17 00:00:00 2001 From: Robin Dunn Date: Thu, 22 Jul 2004 01:04:32 +0000 Subject: [PATCH] mention *TabOrder and Navigate methods git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@28379 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775 --- wxPython/docs/CHANGES.html | 3 +++ wxPython/docs/CHANGES.txt | 6 ++++++ wxPython/docs/MigrationGuide.html | 16 ++++++++++++++++ wxPython/docs/MigrationGuide.txt | 18 ++++++++++++++++++ 4 files changed, 43 insertions(+) diff --git a/wxPython/docs/CHANGES.html b/wxPython/docs/CHANGES.html index eb33bda983..4cf883dfae 100644 --- a/wxPython/docs/CHANGES.html +++ b/wxPython/docs/CHANGES.html @@ -83,6 +83,9 @@ were using these in your apps then please join wxPython-dev and assist with a more modern reimplementation.

Added a new version (0.8.3) of FloatCanvas from Chris Barker. It's now in a subpackage of wx.lib.

+

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.

2.5.1.5

diff --git a/wxPython/docs/CHANGES.txt b/wxPython/docs/CHANGES.txt index 76e2ce2dde..885c84fcf7 100644 --- a/wxPython/docs/CHANGES.txt +++ b/wxPython/docs/CHANGES.txt @@ -97,6 +97,12 @@ Added a new version (0.8.3) of FloatCanvas from Chris Barker. It's now in a subpackage of wx.lib. +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. + + + 2.5.1.5 diff --git a/wxPython/docs/MigrationGuide.html b/wxPython/docs/MigrationGuide.html index 3f50b7f2c8..9727ec6fad 100644 --- a/wxPython/docs/MigrationGuide.html +++ b/wxPython/docs/MigrationGuide.html @@ -777,6 +777,22 @@ 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)
+
diff --git a/wxPython/docs/MigrationGuide.txt b/wxPython/docs/MigrationGuide.txt index 70ee5f4a05..486939494e 100644 --- a/wxPython/docs/MigrationGuide.txt +++ b/wxPython/docs/MigrationGuide.txt @@ -863,3 +863,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) + +