From a729c3447523809786607aa3c62b17059b2c7842 Mon Sep 17 00:00:00 2001 From: Robin Dunn Date: Wed, 4 Feb 2004 02:01:24 +0000 Subject: [PATCH] Updated note about wxWANTS_CHARS git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@25491 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775 --- docs/latex/wx/window.tex | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/docs/latex/wx/window.tex b/docs/latex/wx/window.tex index b209a77e08..b76c6d657a 100644 --- a/docs/latex/wx/window.tex +++ b/docs/latex/wx/window.tex @@ -48,10 +48,14 @@ for this style. } \twocolitem{\windowstyle{wxTRANSPARENT\_WINDOW}}{The window is transparent, that is, it will not receive paint events. Windows only.} \twocolitem{\windowstyle{wxTAB\_TRAVERSAL}}{Use this to enable tab traversal for non-dialog windows.} -\twocolitem{\windowstyle{wxWANTS\_CHARS}}{Use this to indicate that the window -wants to get all char events - even for keys like TAB or ENTER which are -usually used for dialog navigation and which wouldn't be generated without -this style} +\twocolitem{\windowstyle{wxWANTS\_CHARS}}{Use this to indicate that +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 +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 +normal keyboard navigation take place, you should create and send a +wxNavigationKeyEvent in response to the key events for Tab and +Shift-Tab.} \twocolitem{\windowstyle{wxNO\_FULL\_REPAINT\_ON\_RESIZE}}{Disables repainting the window completely when its size is changed - you will have to repaint the new window area manually if you use this style. Currently only has an effect for