diff options
author | Tor Arne Vestbø <tor.arne.vestbo@qt.io> | 2023-03-24 15:26:26 +0100 |
---|---|---|
committer | Tor Arne Vestbø <tor.arne.vestbo@qt.io> | 2023-03-28 16:31:18 +0100 |
commit | b4afba0c3450fd0c14ec7bada098c4e82ca310e7 (patch) | |
tree | 77fc17ff8c6bd43a11551ac17c663dd3cec13c93 /tests/auto/cmake/test_private_includes/main.cpp | |
parent | d34259d9667a621ecde0ec40bef7eec664400a44 (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.
Pick-to: 6.5 6.2
Change-Id: I8a831f5f19adb0625b29b50ebce9c0c6514e93f3
Reviewed-by: Oliver Wolff <oliver.wolff@qt.io>
Diffstat (limited to 'tests/auto/cmake/test_private_includes/main.cpp')
0 files changed, 0 insertions, 0 deletions