don't ignore dialog code when processing Ctrl-keys; otherwise text controls and listboxes never get Ctrl-PageUp/Dn
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@39917 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
@@ -2057,18 +2057,14 @@ bool wxWindowMSW::MSWProcessMessage(WXMSG* pMsg)
|
|||||||
// WM_GETDLGCODE: ask the control if it wants the key for itself,
|
// WM_GETDLGCODE: ask the control if it wants the key for itself,
|
||||||
// don't process it if it's the case (except for Ctrl-Tab/Enter
|
// don't process it if it's the case (except for Ctrl-Tab/Enter
|
||||||
// combinations which are always processed)
|
// combinations which are always processed)
|
||||||
LONG lDlgCode = 0;
|
LONG lDlgCode = ::SendMessage(msg->hwnd, WM_GETDLGCODE, 0, 0);
|
||||||
if ( !bCtrlDown )
|
|
||||||
{
|
|
||||||
lDlgCode = ::SendMessage(msg->hwnd, WM_GETDLGCODE, 0, 0);
|
|
||||||
|
|
||||||
// surprizingly, DLGC_WANTALLKEYS bit mask doesn't contain the
|
// surprizingly, DLGC_WANTALLKEYS bit mask doesn't contain the
|
||||||
// DLGC_WANTTAB nor DLGC_WANTARROWS bits although, logically,
|
// DLGC_WANTTAB nor DLGC_WANTARROWS bits although, logically,
|
||||||
// it, of course, implies them
|
// it, of course, implies them
|
||||||
if ( lDlgCode & DLGC_WANTALLKEYS )
|
if ( lDlgCode & DLGC_WANTALLKEYS )
|
||||||
{
|
{
|
||||||
lDlgCode |= DLGC_WANTTAB | DLGC_WANTARROWS;
|
lDlgCode |= DLGC_WANTTAB | DLGC_WANTARROWS;
|
||||||
}
|
|
||||||
}
|
}
|
||||||
|
|
||||||
bool bForward = true,
|
bool bForward = true,
|
||||||
|
Reference in New Issue
Block a user