diff options
author | Tor Arne Vestbø <tor.arne.vestbo@qt.io> | 2023-03-24 15:26:26 +0100 |
---|---|---|
committer | Qt Cherry-pick Bot <cherrypick_bot@qt-project.org> | 2023-03-28 16:16:34 +0000 |
commit | ca128e25119c0b259d083567c796bfa67b100a42 (patch) | |
tree | 320328ab7ad14ac06ff039d56f28db34261392a8 /examples/widgets/tutorials/widgets/childwidget/CMakeLists.txt | |
parent | 1e393e82c905160ffabd98282aaa8901397ece2b (diff) |
Windows: Send synthetic mouse release after move/resize using right API
The end of a move or resize might happen with the mouse still inside
the non-client area of the window, in which case we correctly resolved
the type to QEvent::NonClientAreaMouseButtonRelease, but we sent it
via QWindowSystemInterface::handleMouseEvent, which sets nonClientArea
of the event to false. This in turn resulted in QGuiApplication sending
a synthetic QEvent::MouseMove in case the position was out of sync,
instead of the correct QEvent::NonClientAreaMouseMove.
This should really be cleaned up on the QWSI level, as there is no
reason to have a dedicated API for handleFrameStrutMouseEvent, when
handleMouseEvent already takes an event type, but for now we fix the
immediate issue in the Windows platform plugin.
Change-Id: I8a831f5f19adb0625b29b50ebce9c0c6514e93f3
Reviewed-by: Oliver Wolff <oliver.wolff@qt.io>
(cherry picked from commit b4afba0c3450fd0c14ec7bada098c4e82ca310e7)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
Diffstat (limited to 'examples/widgets/tutorials/widgets/childwidget/CMakeLists.txt')
0 files changed, 0 insertions, 0 deletions