< Plasma Revision as of 20:46, 31 March 2020 (view source)Markuss (talk | contribs) (Remove fixed showstoppers. Merge the two tablet ones. Clarify NVidia.)← Older edit Revision as of 11:05, 12 May 2020 (view source) Davidedmundson (talk | contribs) (→No (wacom) Tablet support)Newer edit → Line 23: Line 23: == Input == == Input == −=== No (wacom) Tablet support === −KWin lacks integration the tablet support from libinput. Also QtWayland and KWayland lack wrapping the API for it. − === No configurable gestures === === No configurable gestures === X has the ability to accept fake input events to allow programs such as Easystroke. With the new security model of Wayland, such a program would need to be part of the compositor. X has the ability to accept fake input events to allow programs such as Easystroke. With the new security model of Wayland, such a program would need to be part of the compositor. Revision as of 11:05, 12 May 2020 This page tracks the Wayland showstoppers through out the stack Contents 1 General issues 1.1 No vertical / horizontal maximize of Wayland native clients 1.2 No remote support 1.3 NVIDIA 1.4 No Clipboard Manager protocol 2 Input 2.1 No configurable gestures 2.2 No XModmap 3 Plasma 3.1 Native Wayland windows are not restored 3.2 No window thumbnails 3.3 No window move on empty area in breeze 3.4 No activities General issues No vertical / horizontal maximize of Wayland native clients KWin uses NetWM modes internally to do this. Works with Xwayland clients. Would also work for Wayland clients, just the state cannot be exported to Wayland (c.f. Quick tiling). No remote support We don't have an API yet for remote support. Even if we had things like TeamViewer would not work any more. Partly fixed since we now have an API for screencast using a separate KWayland interface. There is also already support in xdg-desktop-portals for convenience of other apps and general support in Flatpaks. What's still missing is an API for remote input. NVIDIA The NVIDIA blob uses a custom EGL extension which Plasma 5.16 added support for. It requires setting the KWIN_DRM_USE_EGL_STREAMS=1 environment variable to activate. Other aspects of the "Wayland experience" with NVIDIA such as XWayland compatibility are outside of our influence. Partly fixed: Requires manual activation. No Clipboard Manager protocol No clipboard history (e.g. Klipper and clipboard plasmoid) and no clipboard sync with KDE Connect. In progress: https://phabricator.kde.org/T4449 Input No configurable gestures X has the ability to accept fake input events to allow programs such as Easystroke. With the new security model of Wayland, such a program would need to be part of the compositor. No XModmap We lack a functionality like XModmap to remap keys. Plasma Native Wayland windows are not restored Session restoring does not include Wayland native windows. Our sessions management recover engine is based on the X Session Management Protocol and there is apparently currently no generic concept to do it on Wayland. But on Qt it's plugin-able and GNOME has according to their wiki an own implementation for some time. No window thumbnails We don't have an API yet for window thumbnails. No window move on empty area in breeze Broke with switch to XdgShellV6. Needs new API added to Qt (native interface), KWayland and Breeze. No activities Activities are probably not a must-have feature, but anyway this is annoying for those who got accustomed to them on X11. Retrieved from "https://community.kde.org/index.php?title=Plasma/Wayland_Showstoppers&oldid=88226" Content is available under Creative Commons License SA 4.0 unless otherwise noted.