Make it possible to check the accepted state of touch events in tests

QTouchEventSequence simulates a QPA touch event, potentially containing
multiple points. (Despite the name, it only calls qt_handleTouchEvent()
once, so it cannot really send a sequence of events; however, one event
can contain multiple touchpoints.) Delivery is synchronous, and we keep
return values through the QWindowSystemInterface::handleTouchEvent()
template functions; so the remaining step is to return a bool from
qt_handleTouchEvent(), so that we can return a bool from commit().
This allows tests to see the same perspective as a platform plugin can:
check whether the event was accepted or not, after delivery is complete.
Some tests in Qt Quick need to start doing that, to enforce correct
behavior in QQuickDeliveryAgent.

[ChangeLog][QtTestLib] QTouchEventSequence::commit() now returns a bool
so that tests can check whether the event was accepted during delivery.

Pick-to: 6.4
Task-number: QTBUG-104656
Change-Id: I9cf87909a3f847dedbdeca257013e309ac19cf0d
Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>

1 files changed, 13 insertions, 7 deletions

diff --git a/src/testlib/qtestcase.qdoc b/src/testlib/qtestcase.qdoc
index fef6b6255c..2c46453968 100644
--- a/src/testlib/qtestcase.qdoc
+++ b/src/testlib/qtestcase.qdoc
@@ -1640,15 +1640,21 @@
 */
 
 /*!
-  \fn void QTest::QTouchEventSequence::commit(bool processEvents)
+    \fn bool QTest::QTouchEventSequence::commit(bool processEvents)
 
-   Commits this sequence of touch events to the event system. Normally there is no need to call this
-   function because it is called from the destructor. However, if autoCommit is disabled, the events
-   only get committed upon explicitly calling this function.
+    Commits this touch event to the event system, and returns whether it was
+    accepted after delivery.
 
-   In special cases tests may want to disable the processing of the events. This can be achieved by
-   setting \a processEvents to false. This results in merely queuing the events, the event loop will
-   not be forced to process them.
+    Normally there is no need to call this function because it is called from
+    the destructor. However, if autoCommit is disabled, the events only get
+    committed upon explicitly calling this function. Another reason to call it
+    explicitly is to check the return value.
+
+    In special cases, tests may want to disable the processing of the event.
+    This can be achieved by setting \a processEvents to false. This results in
+    merely queuing the event: the event loop will not be forced to process it.
+
+    Returns whether the event was accepted after delivery.
 */
 
 /*!