Qt-contributors-summit-2014-Graphics-tablets: Difference between revisions
AutoSpider (talk | contribs) (Add "cleanup" tag) |
m (Categorize) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{Cleanup | reason=Auto-imported from ExpressionEngine.}} | {{Cleanup | reason=Auto-imported from ExpressionEngine.}} | ||
[[Category:QtCS2014]] | |||
Linux: | Linux: | ||
| Line 8: | Line 8: | ||
* touch enabled wacom: 3 devices in xinput | * touch enabled wacom: 3 devices in xinput | ||
* Qt: no distinction between stylus and finger/touch | * Qt: no distinction between stylus and finger/touch | ||
** - | ** -> extend proximity events to have distinction between | ||
Windows: | Windows: | ||
| Line 29: | Line 29: | ||
* does not contain button information | * does not contain button information | ||
* does not contain keyboard modifier | * does not contain keyboard modifier | ||
* windows: wintab - | * windows: wintab -> map button | ||
TabletMove should also be sent with Hover – maybe as TabletProximityMove | TabletMove should also be sent with Hover – maybe as TabletProximityMove | ||
Latest revision as of 17:35, 6 January 2017
| 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