Details
-
Task
-
Resolution: Done
-
Not Evaluated
-
None
-
None
-
6589f2ed0cf78c9b8a5bdffcdc458dc40a974c60 (qt/qtbase/dev), 5af836aea (dev), 1a1b7cb71 (6.8), 4322496f7 (dev), 746f5fccc (6.8), 973b5a99f (6.8), f036aabf5 (dev)
Description
QScreen, QTouchDevice, QTabletDevice etc. are currently standalone classes, but they should be related to each other by belonging to a single-rooted inheritance tree, and also be able to have links to each other to express the idea that a particular input device belongs to a particular screen, which devices are accessible to which users, etc.
In QtQuick we have QQuickPointerDevice, but it needs to be able to hold a pointer to a QPointerDevice (or QPointingDevice) that lives in qtbase.
Attachments
Issue Links
- depends on
-
QTBUG-63363 QPointingDevices for the trackpad and mouse are dynamically instantiated on macOS
-
- Reported
-
- duplicates
-
QTBUG-46412 expose a complete list of QInputDevice
-
- Closed
-
- is required for
-
QTBUG-69422 Input Handling Changes in Qt 6
-
- Closed
-
-
QTBUG-72173 Refactor the QEvent hierarchy to make input events more like QQuickPointerEvents in Qt 6
-
- Closed
-
- relates to
-
QTBUG-78839 Map touchscreen input device to specific display
-
- Reported
-
-
QTBUG-87646 WheelHandler doesn't work correctly with TouchPad
-
- Closed
-
- resulted in
-
QTBUG-112432 wayland plugin should distinguish touchpads from mice, etc.
-
- Reported
-
-
QTBUG-115207 Properly register the input devices on Wayland
-
- Reported
-
-
QTBUG-119029 Get rid of QXcbConnection::TouchDeviceData; pre-construct QEventPoints in xcb plugin
-
- Reported
-