Shawn Rutledge 0f94430a0f testlib: make it possible to test double-clicks with discrete events ... The timestamp will no longer be incremented by 500ms after a mouse release if the delay has been explicitly specified. The default delay is 1 ms since f5010c49a3 but the running timestamp was unconditionally post-incremented by 500ms after every mouse release, to prevent double-clicks, which were always deemed as unintended (because we have a mouseDClick function for that). Now, we do that 500ms increment only if the user has not provided a delay value in the function argument at all. We have often found it useful in our own tests to generate double-clicks "the hard way", by sending indivdual events, so as to be able to check state in some target object at each step, as shown in the new snippet. [ChangeLog][QtTest] QTest::mouseRelease() and mouseClick() can now be used to test double-clicks, by specifying a realistic timestamp delay. Fixes: QTBUG-102441 Change-Id: I8e8d242061f79efb4c6e02638645e03661a9cd92 Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>		2022-10-16 08:36:03 +02:00
..
initmain	Use SPDX license identifiers	2022-05-16 16:37:38 +02:00
outformat	Use SPDX license identifiers	2022-05-16 16:37:38 +02:00
qabstractitemmodeltester	Change the license of all CMakeLists.txt and *.cmake files to BSD	2022-08-23 23:58:42 +02:00
qsignalspy	Port from container.count()/length() to size()	2022-10-04 07:40:08 +02:00
selftests	testlib: make it possible to test double-clicks with discrete events	2022-10-16 08:36:03 +02:00
CMakeLists.txt	Change the license of all CMakeLists.txt and *.cmake files to BSD	2022-08-23 23:58:42 +02:00