Qt-contributors-summit-2014-Graphics-tablets

From Qt Wiki
Jump to: navigation, search
This article may require cleanup to meet the Qt Wiki's quality standards. Reason: Auto-imported from ExpressionEngine.
Please improve this article if you can. Remove the {{cleanup}} tag and add this page to Updated pages list after it's clean.

Linux:

  • 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

Windows:

  • 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

Mac:

  • unknown

QTabletEvent:

  • 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).

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
https://bugreports.qt.io/browse/QTBUG-39459
https://bugreports.qt.io/browse/QTBUG-39581
https://bugreports.qt.io/browse/QTBUG-39579
https://bugreports.qt.io/browse/QTBUG-39578
https://bugreports.qt.io/browse/QTBUG-39573
https://bugreports.qt.io/browse/QTBUG-39572
https://bugreports.qt.io/browse/QTBUG-39571
https://bugreports.qt.io/browse/QTBUG-39570