Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-51618

Android: the stylus sends QTabletEvent but not QMouseEvent

    XMLWordPrintable

Details

    • 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

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-39572 XCB: Touch subdevice of a Wacom Intuos Pro 5 tablet is recognized as a tablet instead of a touch device

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-51617 QMouseEvent::source() reports MouseEventNotSynthesized when it comes from a Wacom tablet

          • P3: Somewhat important - Should be fixed, but doesn't affect the release in any way.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-100788 TapHandler tapped signal is emitted twice when using a stylus

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed
          resulted from

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-38379 Android: No move events from Galaxy Note SPen in widgets app

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Closed
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              srutledg Shawn Rutledge
              srutledg Shawn Rutledge
              Votes:
              3 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes