path: root/tests/auto
diff options
authorShawn Rutledge <shawn.rutledge@qt.io>2019-05-08 14:56:24 +0200
committerShawn Rutledge <shawn.rutledge@qt.io>2019-05-09 09:18:51 +0000
commit17237efaefabe924599abe00e92d8b54032d7915 (patch)
tree3e389ccc408d490fd855a2b6a202aefd3ec827af /tests/auto
parentd12cc4f6b58ecb5f44458002fe9b74d0c84f10ae (diff)
Document TapHandler.tapped and [single|double]Tapped eventPoint argument
Amends b8fd580cb3453b3850c36765c4b2537538d2f4f8 to add documentation. The eventPoint is important to get ephemeral state from the pointing device: which button was released (thus triggering the tap), which device it was, and where the release occurred. Users may expect to use the point property, but QQuickHandlerPoint::reset(QQuickEventPoint *) resets every property of the point at the same time, so the architecture currently does not allow for mixed state, i.e. having correct button state but still holding leftover position information. It may be surprising for users, but the changes to the point property are an atomic transaction that occurs before the signal. Task-number: QTBUG-61749 Task-number: QTBUG-64847 Change-Id: I33e0e232084beba8e10d8b02fa3bf85f36293358 Reviewed-by: Jan Arve Sæther <jan-arve.saether@qt.io>
Diffstat (limited to 'tests/auto')
0 files changed, 0 insertions, 0 deletions