https://bugs.kde.org/show_bug.cgi?id=429079
Jason G. <killert...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |killert...@gmail.com
--- Comment #18 from Jason G. <killert...@gmail.com> ---
Linuxwacom developer reporting in with some clarification on the status of
tablet support in Wayland.
The "tablet_unstable_v2" protocol that was linked above is pretty much unstable
only in name at this point*. XWayland, GNOME, and wlroots (Sway, etc.) have
supported the compositor half of the protocol for a few years now. Basic
support landed in the KWin compositor in mid-2020 as part of their 5.19 release
and then extended for the early-2021 release of 5.21. On the toolkit obviously
GTK3 has supported it for some time, but more interesting is "basic support" in
Qt 5.15 (see
https://github.com/qt/qtwayland/commit/222455cd643c128fa9730c9c527a7fdcadd0acfe
for specifics).
All the upstream pieces should be in place for tablets to work with Krita in
Wayland. Note, however, that it may be buggy even if you can get it working
somehow. The KWin/Qt Wayland tablet code has had very little real-world use at
this point and there are bound to be little problems that get discovered as
more people are able to test them out.
* Transitioning a protocol from "unstable" to "stable" is an API break that
requires all compositors / toolkits to update. Its a lot of effort for
basically zero benefit. Wayland-protocols recently replaced "unstable" with
"staging" to fix this issue for new protocols, but there are lots of "stable
unstable" protocols like ours that may never migrate into the "stable"
directory.
--
You are receiving this mail because:
You are watching all bug changes.
