diff options
| author | Michal Klocek <michal.klocek@qt.io> | 2023-10-27 21:26:25 +0200 |
|---|---|---|
| committer | Michal Klocek <michal.klocek@qt.io> | 2023-11-01 20:28:24 +0100 |
| commit | 567e9b2026c42f823d0f71c691746fe583dc8e4c (patch) | |
| tree | a165c9e71844385149305bc891557b4edc1b667d /src/testlib | |
| parent | 38ce08aa8e98035ad7414130d82458ab8b228514 (diff) | |
Doc: Fix QTest::createTouchDevice docs
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.6 6.5
Change-Id: I3a0400288d76b7c95659d6b6ea260eff3233ebf1
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
Diffstat (limited to 'src/testlib')
| -rw-r--r-- | src/testlib/qtestcase.qdoc | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/src/testlib/qtestcase.qdoc b/src/testlib/qtestcase.qdoc index 9b539deb1e..7c50461849 100644 --- a/src/testlib/qtestcase.qdoc +++ b/src/testlib/qtestcase.qdoc @@ -1635,10 +1635,10 @@ Creates a dummy touch device of type \a devType with capabilities \a caps for simulation of touch events. - The touch device will be registered with the QPA window system interface, - and deleted automatically when the QCoreApplication is deleted. So you - should typically use createTouchDevice() to initialize a QPointingDevice - member variable in your test case class, and use the same instance for all tests. + The touch device will be registered with the Qt window system interface. + You should typically use createTouchDevice() to initialize a QPointingDevice + member variable in your test case class, use the same instance for all tests and + delete it when no longer needed. \sa QTest::QTouchEventSequence, touchEvent() */ |