aboutsummaryrefslogtreecommitdiffstats
path: root/tests/auto/quick/pointerhandlers/qquickpinchhandler/data
Commit message (Collapse)AuthorAgeFilesLines
* Correct license for test filesLucie Gérard2024-02-275-5/+5
| | | | | | | | | | | | | | According to QUIP-18 [1], all test files should be LicenseRef-Qt-Commercial OR GPL-3.0-only [1]: https://contribute.qt-project.org/quips/18 Pick-to: 6.7 Task-number: QTBUG-121787 Change-Id: I26d72e8de04d4c7c57b3b7838af5d033265de5ba Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io> Reviewed-by: Kai Köhne <kai.koehne@qt.io> Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
* Fix PinchHandler.persistentTranslation; test cumulative native gesturesShawn Rutledge2023-04-111-1/+8
| | | | | | | | | | | | | | | | | | | | | Since we do not want persistentTranslation to be always the same as target.position, clearly we cannot use xAxis/yAxis to store the initial target position: thus the startPos() function was wrong, and is now removed. We need to store it in a separate m_startTargetPos variable like DragHandler does, and as PinchHandler did before 7867a683fcb938939fb2837a26ac8e1941e3fe08. Add an internal doc comment to clarify the arguments to QQuickItemPrivate::adjustedPosForTransform(). tst_QQuickPinchHandler::cumulativeNativeGestures() now checks the result of adjustedPosForTransform(): how far the target item moved. Pick-to: 6.5 Fixes: QTBUG-111220 Change-Id: I04237cb82a1abaaeab873a0d887acaf322f262ce Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
* Improve DragHandler tests for easier troubleshootingShawn Rutledge2023-01-091-3/+11
| | | | | | | | | | | - Sometimes you just need to see the touchpoints and centroids - Delay long enough to see them - Avoid QTRY_COMPARE when we're sure the event was already flushed - Fix indentation Pick-to: 6.5 Change-Id: I307963378c29fb285190657e7a0693888ad7c48c Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
* Stabilize tst_QQuickPinchHandler::scaleThreeFingers with dragThresholdShawn Rutledge2022-12-121-1/+2
| | | | | | | | | | Local behavior has been different than on CI or with Xephyr: high-dpi screens have a larger drag threshold even when QT_ENABLE_HIGHDPI_SCALING=0 and QT_SCALE_FACTOR=1. This should make the test DPI-independent. Change-Id: I4c0ee5b47a0635fc6ca9cc881993bf0a82b0624b Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
* PinchHandler null target: remember accumulated scale between pinchesShawn Rutledge2022-11-171-0/+33
| | | | | | | | | | | | | | | | | | | | This restores behavior from b4d31c9ff5f0c5821ea127c663532d9fc2cae43e which got broken in fc636af3a723ee8b4ee42cf71864ae0df5ca4621. As documented, PinchHandler.scale is the accumulated scale that would be applied to the target item (even if there is no target), whereas activeScale is the scale during one pinch gesture. After the first gesture, these two values are supposed to diverge, even if there is no target; that way you can bind scale to some property, to scale something else in the same way that PinchHandler would normally scale its target. Pick-to: 6.2 6.4 Fixes: QTBUG-108549 Task-number: QTBUG-68941 Task-number: QTBUG-92064 Change-Id: I32ff37e394fd8466128603eddd5697ba1cc1a0ed Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
* Make tst_QQuickPinchHandler::scale easier to maintainShawn Rutledge2022-11-171-2/+28
| | | | | | | | | | | | | | | | | | | | | | | | I kept forgetting why there were odd indented blocks, why it was letting the QTouchEventSequence go out of scope and making a new one, and why that resulted in an out-of-bounds pinch. It works well enough to just drag the second touchpoint all the way down into the lower-right corner: without maximumScale being set, it goes to 5.75, so we can verify that setting maximumScale limits it to 4. While we're at it: - use QQuickTest::showView() - better comments - loop instead of copy-pasting blocks of code - show the touchpoints - slow it down enough to see them when cat. logging is turned on - get rid of that weird opacity hack - check pinchHandler's own scale() and activeScale() properties Amends f289141524d9331bdafd9f88d95e0fa9b29ccdee Pick-to: 6.2 6.4 Change-Id: I799c256286f4408f89c0502db33c9f676a2ce1b1 Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
* tst_qquickpinchhandler: rename root.scale property to pinchScaleShawn Rutledge2022-11-171-3/+3
| | | | | | | | | | | | It doesn't look sensible to hide the existing Item.scale property. PinchArea's properties are directly accessible in test code, but maybe there's some sense in testing the onActiveChanged and onUpdated signals. Amends f289141524d9331bdafd9f88d95e0fa9b29ccdee which copied code from tst_qquickpincharea. Pick-to: 6.2 6.4 Change-Id: I108fffc9b99b4eebc949fe11c9b7dd649d98f59a Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
* tst_QQuickPinchHandler::scaleThreeFingers: stop using root propertiesShawn Rutledge2022-11-171-4/+0
| | | | | | | | | | It's confusing to hide root's Item.scale property with another property; and the others aren't needed either. Use the PinchHandler properties directly. Amends f289141524d9331bdafd9f88d95e0fa9b29ccdee which copied code from tst_qquickpincharea (which still has the same silliness). Change-Id: Ib30fd81314f14c235948179462cd4a2dd742a65d Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
* PinchHandler: Enforce min/max scale limits with native gesturesShawn Rutledge2022-09-011-1/+1
| | | | | | | | | | | So far the qBound() using m_minimumScale and m_maximumScale was only applied for normal pointer events: there were no limits when using a touchpad that sends native gestures. Pick-to: 6.2 6.3 6.4 Fixes: QTBUG-106110 Change-Id: Ibf8d955e5f1dac517e0a3e9588fb117d83f443a6 Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
* Use SPDX license identifiersLucie Gérard2022-06-114-108/+8
| | | | | | | | | | | | Replace the current license disclaimer in files by a SPDX-License-Identifier. Files that have to be modified by hand are modified. License files are organized under LICENSES directory. Pick-to: 6.4 Task-number: QTBUG-67283 Change-Id: I63563bbeb6f60f89d2c99660400dca7fab78a294 Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
* DragHandler: don't try to handle native gesture eventsShawn Rutledge2021-03-261-0/+62
| | | | | | | | | | | | | | | | | | No gesture handling has been implemented in DragHandler (although we could). It just made the target item jump unintentionally. QQuickMultiPointHandler::wantsPointerEvent() returns true for gestures, because PinchHandler handles them, and the pattern is that base classes only rule out some kinds of events but leave the final decision up to the leaf class. The autotest has to use a touchpad now, not the primary pointing device, because QQuickPointerDeviceHandler::wantsPointerEvent() returns false if pointerType != Finger and acceptedButtons() is not satisfied. Fixes: QTBUG-92165 Change-Id: I984de750c9ae892f3ee61c7ed5b3ac4a7d187024 Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
* PinchHandler: Avoid unwanted translations when axes are disabledShawn Rutledge2019-01-281-1/+9
| | | | | | Fixes: QTBUG-72822 Change-Id: I2773ba14fcb24a47fe2ec04860b4aa305a051453 Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
* Add a C++ autotest for PinchHandlerShawn Rutledge2018-08-023-0/+181
Adapted from the PinchArea test. cancel() does not work, TDB if we want to support that Done-with: Jan-Arve Sæther <jan-arve.saether@qt.io> Task-number: QTBUG-69134 Change-Id: I63dfba7b327220b9f032f19c588cc19ebdfd95c2 Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-19 17:32:40 +0000