Allow WM_SYSKEYDOWN to still be processed by MSWDefWindowProc, even if

it was handled by an event handler.  This allows the magic Windows
keys (such as Alt-space for the system menu, Alt or F10 to activate
the menu bar, Alt-F4 to send WM_CLOSE, etc.) to still work properly.


git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/branches/WX_2_4_BRANCH@17601 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Robin Dunn
2002-10-21 22:19:07 +00:00
parent 3fe4f9bf40
commit e771b7e4ac

View File

@@ -2612,9 +2612,10 @@ long wxWindowMSW::MSWWindowProc(WXUINT message, WXWPARAM wParam, WXLPARAM lParam
if ( m_lastKeydownProcessed )
{
processed = TRUE;
break;
}
if ( !processed )
{
switch ( wParam )
{
// we consider these message "not interesting" to OnChar, so
@@ -2655,7 +2656,6 @@ long wxWindowMSW::MSWWindowProc(WXUINT message, WXWPARAM wParam, WXLPARAM lParam
// to the control's default window proc - otherwise
// built-in keyboard handling won't work
processed = FALSE;
break;
#ifdef VK_APPS
@@ -2675,8 +2675,10 @@ long wxWindowMSW::MSWWindowProc(WXUINT message, WXWPARAM wParam, WXLPARAM lParam
default:
// do generate a CHAR event
processed = HandleChar((WORD)wParam, lParam);
}
}
if (message == WM_SYSKEYDOWN) // Let Windows still handle the SYSKEYs
processed = FALSE;
break;
case WM_SYSKEYUP: