Document wxWindow::Navigate() instead of generation

of a navigation event in the text on wxWANTS_CHARS.


git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@45374 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Robert Roebling
2007-04-10 08:03:39 +00:00
parent 346d8899f3
commit 06354b5621

View File

@@ -62,10 +62,10 @@ events. Windows only.}
the window wants to get all char/key events for all keys - even for the window wants to get all char/key events for all keys - even for
keys like TAB or ENTER which are usually used for dialog navigation keys like TAB or ENTER which are usually used for dialog navigation
and which wouldn't be generated without this style. If you need to and which wouldn't be generated without this style. If you need to
use this style in order to get the arrows or etc., but would still like to have use this style in order to get the arrows or etc., but would still like
normal keyboard navigation take place, you should create and send a to have normal keyboard navigation take place, you should call
wxNavigationKeyEvent in response to the key events for Tab and \helpref{Navigate}{wxwindownavigate} in response to the key events for
Shift-Tab.} Tab and Shift-Tab.}
\twocolitem{\windowstyle{wxNO\_FULL\_REPAINT\_ON\_RESIZE}}{On Windows, this style used to disable repainting \twocolitem{\windowstyle{wxNO\_FULL\_REPAINT\_ON\_RESIZE}}{On Windows, this style used to disable repainting
the window completely when its size is changed. Since this behaviour is now the default, the style is now obsolete the window completely when its size is changed. Since this behaviour is now the default, the style is now obsolete
and no longer has an effect.} and no longer has an effect.}