b1481a1663
When QGuiApplicationPrivate::processTouchEvent() sees that the touch event was not handled, and calls processMouseEvent(), the latter uses the QEventPoint with pointId 0 regardless of the original touchpoint ID. Now it updates the persistent QEventPoint from the original touchpoint so that a double-click event will not be ruled out because of the timestamp delta or position delta (movement since press) being too large. Fixes: QTBUG-125993 Pick-to: 6.7 6.5 Change-Id: I8e9b007818107ac2329454e0ccfb2ac9e506b617 Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io> (cherry picked from commit 2a0b907f11b9c0ad46322ba06482861423246d93) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org> |
||
|---|---|---|
| .. | ||
| auto | ||
| baseline | ||
| benchmarks | ||
| global | ||
| libfuzzer | ||
| manual | ||
| shared | ||
| testserver | ||
| CMakeLists.txt | ||
| README | ||
README
This directory contains autotests and benchmarks based on Qt Test. In order
to run the autotests reliably, you need to configure a desktop to match the
test environment that these tests are written for.
Linux X11:
* The user must be logged in to an active desktop; you can't run the
autotests without a valid DISPLAY that allows X11 connections.
* The tests are run against a KDE3 or KDE4 desktop.
* Window manager uses "click to focus", and not "focus follows mouse". Many
tests move the mouse cursor around and expect this to not affect focus
and activation.
* Disable "click to activate", i.e., when a window is opened, the window
manager should automatically activate it (give it input focus) and not
wait for the user to click the window.