Details
-
Bug
-
Resolution: Done
-
P2: Important
-
5.6.0 Alpha
-
f931e5e72d4617023bbea46cba2c0d61bb1efa4f
Description
After fixing QTBUG-38379 this has been the case. The documentation (erroneously: QTBUG-47007) says that if the QTabletEvent is not accepted, a QMouseEvent will be sent. But it turns out there is no cross-platform code to do this; in fact, the platform plugins which can handle Wacom tablets are unconditionally sending a QMouseEvent after every QTabletEvent (see QXcbConnection::xi2HandleTabletEvent() and QNSView::handleMouseEvent / handleTabletEvent, for example). But not on Android so far. So, you can't interact with any widgets which only handle mouse events, using the stylus, on Galaxy Note devices. It's OK for drawing (e.g. the tablet example works fine), and in fact a well-designed drawing app should probably handle touch and stylus uniquely. But some people get in the habit of using the stylus for everything, and that works in native Android apps.
Attachments
Issue Links
- relates to
-
QTBUG-39572 XCB: Touch subdevice of a Wacom Intuos Pro 5 tablet is recognized as a tablet instead of a touch device
- Closed
-
QTBUG-51617 QMouseEvent::source() reports MouseEventNotSynthesized when it comes from a Wacom tablet
- Closed
-
QTBUG-100788 TapHandler tapped signal is emitted twice when using a stylus
- Closed
- resulted from
-
QTBUG-38379 Android: No move events from Galaxy Note SPen in widgets app
- Closed
- resulted in
-
QTBUG-129998 synthesis of mouse events after unaccepted QTabletEvents doesn't work on some platforms
- Reported