Details
-
Task
-
Resolution: Done
-
P2: Important
-
None
-
6ad66140b1e63fa6e21c7f33d845a472c4390823 9a096cba223936c81c2c3392265681c78e63617e da9e02eb83ea6eecf3cdb16b11241c91f5029380
Description
The Krita authors have reported that they need to reject each QTabletEvent and wait for the mouse event that follows, in order to find out which buttons are pressed. The reason is that tablet and stylus buttons are sometimes used during the drawing process itself, not just as mouse buttons for conventional UI elements. So it makes sense to have the buttons in the event, since this information is already known when the event is created.
The trouble with rejecting tablet events is that the queue is cleared at that point, so some events will be discarded, and the result is not very smooth drawing.
Attachments
Issue Links
- is duplicated by
-
QTBUG-4097 QTabletEvent: Add a buttons() and modifiers() function to return the buttons and modifiers respectively
- Closed
- relates to
-
QTBUG-39459 ensure that QTabletEvent timestamp comes consistently from the device and has the same units
- Closed