Update outdated comment in QEventDispatcherWin32::processEvents
The reason for the explicit qt_GetMessageHook call is not related to Windows CE anymore. It is a work-around used by the Direct2D integration. Change-Id: I489665741fc673ab9d29b35a0c02c51f2a9e9288 Reviewed-by: Maurice Kalinowski <maurice.kalinowski@qt.io>
This commit is contained in:
parent
b4a1336bb0
commit
b6c7defd6c
@ -610,7 +610,7 @@ bool QEventDispatcherWin32::processEvents(QEventLoop::ProcessEventsFlags flags)
|
||||
}
|
||||
}
|
||||
if (haveMessage) {
|
||||
// WinCE doesn't support hooks at all, so we have to call this by hand :(
|
||||
// The Direct2d integration unsets getMessageHook. See QTBUG-42428
|
||||
if (!d->getMessageHook)
|
||||
(void) qt_GetMessageHook(0, PM_REMOVE, reinterpret_cast<LPARAM>(&msg));
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user