summaryrefslogtreecommitdiffstats
path: root/src/corelib/doc/src/filestorage.qdoc
diff options
context:
space:
mode:
authorRichard Moe Gustavsen <richard.gustavsen@theqtcompany.com>2015-02-12 13:07:24 +0100
committerRichard Moe Gustavsen <richard.gustavsen@theqtcompany.com>2015-02-15 11:12:50 +0000
commitab3113b679922e5232d56a9532c4330b8986e493 (patch)
treefdd253a1509dbcd1926a6581f9263f7c3034ef81 /src/corelib/doc/src/filestorage.qdoc
parent6342c4a1836f76db43e09a89239d73eda44f414a (diff)
QGuiApplication: revert b8d0fac5a9 (mouse event handling)
The current attempt to fix the problem described in b8d0fac5a9 has shown to have unforeseen issues. The assert in the patch has been triggered in user code (see bug report), which, when looking more closely, shows that the assert cannot be guaranteed for all cases. E.g if user code (or Qt drag'n'drop code) starts a new event loop upon receiving the move event, this can deliver new mouse events before the move returns, which will trigger the assert. So it seems like the most correct solution is to *post* the second button event after all (directly trailing the move event), to at least make sure mouse events are being delivered in the correct order. The crash that caused the original change will need to be fixed by other means. Task-number: QTBUG-38597 Change-Id: I47633d1ea310b7c16e937ef0404d9954281452c3 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@theqtcompany.com> Reviewed-by: Laszlo Agocs <laszlo.agocs@theqtcompany.com>
Diffstat (limited to 'src/corelib/doc/src/filestorage.qdoc')
0 files changed, 0 insertions, 0 deletions