From 3d89fa97cc49164e3b4e4be0ee7096318ee48343 Mon Sep 17 00:00:00 2001 From: Michal Klocek Date: Mon, 3 Aug 2020 18:00:03 +0200 Subject: [PATCH] Remove InfoFlag from docs It seem to be a leftover after 4e400369. Change-Id: I1c12bfa70cb3716d5cd9d1306db23242b58f3096 Reviewed-by: Shawn Rutledge --- src/gui/kernel/qevent.cpp | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/src/gui/kernel/qevent.cpp b/src/gui/kernel/qevent.cpp index 9e8fc196490..517233482f0 100644 --- a/src/gui/kernel/qevent.cpp +++ b/src/gui/kernel/qevent.cpp @@ -4260,10 +4260,13 @@ QTouchEvent::~QTouchEvent() Returns the unique ID of this touch point or token, if any. It is often invalid (see \l {QPointingDeviceUniqueId::isValid()} {isValid()}), - because touchscreens cannot uniquely identify fingers. But when the - \l {TouchPoint::InfoFlag} {Token} flag is set, it is expected to uniquely - identify a specific token (fiducial object). When it comes from a QTabletEvent, - it identifies the serial number of the stylus in use. + because touchscreens cannot uniquely identify fingers. + + When it comes from a QTabletEvent, it identifies the serial number of the + stylus in use. + + It may identify a specific token (fiducial object) when the TUIO driver is + in use with a touchscreen that supports them. \sa flags */