Difference between revisions of "Qt-contributors-summit-2014-Graphics-tablets"

From Qt Wiki
Jump to: navigation, search
Line 1: Line 1:
* 5 ways of accessing devices
* evdev, wacom, proprietary
* touch enabled wacom: 3 devices in xinput
* Qt: no distinction between stylus and finger/touch
** -> extend proximity events to have distinction between
* 2 protocols
* wintab (deprecated)
* e-ink (now, originally hand writing)
* drivers potentially override each other
* lacking transformation of value ranges and rotation direction
* wintab at least has time information in the low level event
* unknown
* does not contain button information
* does not contain keyboard modifier
* windows: wintab -> map button
TabletMove should also be sent with Hover – maybe as TabletProximityMove
Tablets and events should have a manual test app
Stylus hover: cannot read rotation, z-coordinate, use for paning/zooming
Potentially used and worked around by many applications (also commercial).
[https://docs.google.com/document/d/1_K9hBvpvfamFobq4dVnn5_wXNeYE5oHPVDJJ7HbZsJQ/edit Google doc with a list of bugs and hacks that Krita needs] ''[docs.google.com]''
And now we have the following bugs in Jira (label: qtcs14tablet)
https://bugreports.qt.io/browse/QTBUG-39458<br />https://bugreports.qt.io/browse/QTBUG-39459<br />https://bugreports.qt.io/browse/QTBUG-39581<br />https://bugreports.qt.io/browse/QTBUG-39579<br />https://bugreports.qt.io/browse/QTBUG-39578<br />https://bugreports.qt.io/browse/QTBUG-39573<br />https://bugreports.qt.io/browse/QTBUG-39572<br />https://bugreports.qt.io/browse/QTBUG-39571<br />https://bugreports.qt.io/browse/QTBUG-39570

Revision as of 14:00, 24 February 2015