Failure to do this can have catastrophic consequences, e.g. embedded ActiveX
IE controls may stop working -- even after resuming the normal message
dispatching.
Closes #14027.
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@70690
c3d73ce0-8a6f-49c7-b76d-
6d57e0e08775
}
// choose a wxEventCategory for this Windows message
}
// choose a wxEventCategory for this Windows message
switch (msg.message)
{
#if !defined(__WXWINCE__)
switch (msg.message)
{
#if !defined(__WXWINCE__)
case WM_MBUTTONUP:
case WM_MBUTTONDBLCLK:
case WM_MOUSEWHEEL:
case WM_MBUTTONUP:
case WM_MBUTTONDBLCLK:
case WM_MOUSEWHEEL:
- cat = wxEVT_CATEGORY_USER_INPUT;
+ processNow = (eventsToProcess & wxEVT_CATEGORY_USER_INPUT) != 0;
- cat = wxEVT_CATEGORY_TIMER;
+ processNow = (eventsToProcess & wxEVT_CATEGORY_TIMER) != 0;
// by the system.
// there are too many of these types of messages to handle
// them in this switch
// by the system.
// there are too many of these types of messages to handle
// them in this switch
- cat = wxEVT_CATEGORY_UI;
+ processNow = (eventsToProcess & wxEVT_CATEGORY_UI) != 0;
- cat = wxEVT_CATEGORY_UNKNOWN;
+ {
+ // Process all the unknown messages. We must do it because
+ // failure to process some of them can be fatal, e.g. if we
+ // don't dispatch WM_APP+2 then embedded IE ActiveX
+ // controls don't work any more, see #14027. And there may
+ // be more examples like this, so dispatch all unknown
+ // messages immediately to be safe.
+ processNow = true;
+ }
}
// should we process this event now?
}
// should we process this event now?
- if (cat & eventsToProcess)
{
if ( !wxTheApp->Dispatch() )
break;
{
if ( !wxTheApp->Dispatch() )
break;