1berry/qtbase
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Doc: Fix QTest::createTouchDevice docs

Browse Source 
After the introduction of QInputDevice class the returned
QPointingDevice object from QTest::createTouchDevice()
call is no longer automatically deleted when the
QCoreApplication is deleted. Moreover, this function does
not really go thorough qpa but simply registers the device with
QWindowSystemInterface::registerInputDevice() (which is
actually also used from qpa plugins when new device is plugged)

Pick-to: 6.5
Change-Id: I3a0400288d76b7c95659d6b6ea260eff3233ebf1
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
(cherry picked from commit 567e9b2026c42f823d0f71c691746fe583dc8e4c)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
This commit is contained in:
Michal Klocek 2023-10-27 21:26:25 +02:00 committed by Qt Cherry-pick Bot
parent aecd210c75
commit 9c1fb39c9c
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
src/testlib/qtestcase.qdoc
View File

@ -1635,10 +1635,10 @@
Creates a dummy touch device of type \a devType with capabilities \a caps for Creates a dummy touch device of type \a devType with capabilities \a caps for
simulation of touch events. simulation of touch events.
The touch device will be registered with the QPA window system interface, The touch device will be registered with the Qt window system interface.
and deleted automatically when the QCoreApplication is deleted. So you You should typically use createTouchDevice() to initialize a QPointingDevice
should typically use createTouchDevice() to initialize a QPointingDevice member variable in your test case class, use the same instance for all tests and
member variable in your test case class, and use the same instance for all tests. delete it when no longer needed.
\sa QTest::QTouchEventSequence, touchEvent() \sa QTest::QTouchEventSequence, touchEvent()
*/ */