3d70925ee5
In rare cases, the Windows event loop can be spinning inside the inner loop and the message hook is never called. This can be triggered on the Direct2D platform by opening 32+ window handles. The issue can be worked around by using the same approach Windows CE uses: don't rely on the message hook to inform the event loop that the post message has been delivered. Instead, uninstall the hook and let it be called directly by the event loop. Task-number: QTBUG-42428 Change-Id: I10280126dd50729bc260aa5f7029549e2e061c01 Reviewed-by: Louai Al-Khanji <louai.al-khanji@theqtcompany.com> Reviewed-by: Friedemann Kleint <Friedemann.Kleint@theqtcompany.com> |
||
---|---|---|
.. | ||
animation | ||
arch | ||
codecs | ||
doc | ||
global | ||
io | ||
itemmodels | ||
json | ||
kernel | ||
mimetypes | ||
plugin | ||
statemachine | ||
thread | ||
tools | ||
xml | ||
corelib.pro | ||
eval.pri | ||
Qt5Config.cmake.in | ||
Qt5CoreConfigExtras.cmake.in | ||
Qt5CoreConfigExtrasMkspecDir.cmake.in | ||
Qt5CoreConfigExtrasMkspecDirForInstall.cmake.in | ||
Qt5CoreMacros.cmake | ||
Qt5CTestMacros.cmake | ||
QtCore.dynlist |