You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I'm not mistaken, it looks like KDE uses the input-method protocol as well for emulating a virtual keyboard. Assuming that's the case, if wtype does add support for it, it would benefit programs like tessen which aim to support auto-typing of data on wlroots based compositors and on KDE.
I was trying to find out why wtype is not working under KDE and found my way here. So if I'm understanding correctly, wtype currently supports neither KDE nor Gnome because neither supports virtual-keyboard-unstable-v1? That's rather disappointing TBH.
I'm not trying to be a dick about it, but frankly wtype is not going to be very useful if the protocol it relies on is not supported by the two most popular DEs out there. I strongly agree with the opinion here that this should at least be made clear in README.
This issue tracker presents an overview of the state of autotyping protocols and their support in various desktop environments and window managers on Wayland.
What about ydotool, they changed it into a client/daemon setup so without looking into it... this could allow for a better setup in terms of not giving users direct access to /dev/uinput ... but ofc there is still a part that interfaces with it.
Would this change your view on it (original request: ayushnix/tessen#20)? @ayushnix
Activity
emersion commentedon Sep 22, 2021
Quick demo: https://git.sr.ht/~emersion/wl-ime-type
ayushnix commentedon Feb 24, 2022
If I'm not mistaken, it looks like KDE uses the input-method protocol as well for emulating a virtual keyboard. Assuming that's the case, if wtype does add support for it, it would benefit programs like tessen which aim to support auto-typing of data on wlroots based compositors and on KDE.
cyqsimon commentedon Aug 29, 2022
I was trying to find out why wtype is not working under KDE and found my way here. So if I'm understanding correctly, wtype currently supports neither KDE nor Gnome because neither supports
virtual-keyboard-unstable-v1? That's rather disappointing TBH.I'm not trying to be a dick about it, but frankly wtype is not going to be very useful if the protocol it relies on is not supported by the two most popular DEs out there. I strongly agree with the opinion here that this should at least be made clear in README.
ayushnix commentedon Aug 29, 2022
This issue tracker presents an overview of the state of autotyping protocols and their support in various desktop environments and window managers on Wayland.
jarlucmat commentedon Mar 13, 2024
+1 for KDE support.
OctoRocket commentedon Jun 10, 2024
It is worth mentioning that the example uses zwp-input-method-v2, which isn't actually supported by KWin. KWin only supports zwp-input-method-v1.
novski commentedon Jul 31, 2024
for KDE this should work https://github.com/jinliu/kdotool
jarlucmat commentedon Aug 5, 2024
They state that they will not support keyboard commands. The goal is to control windows through Kwin API
HoroTW commentedon Oct 25, 2024
What about ydotool, they changed it into a client/daemon setup so without looking into it... this could allow for a better setup in terms of not giving users direct access to /dev/uinput ... but ofc there is still a part that interfaces with it.
Would this change your view on it (original request: ayushnix/tessen#20)? @ayushnix
ayushnix commentedon Oct 25, 2024
@HoroTW I'm not working on tessen these days. 😅
HoroTW commentedon Nov 15, 2024
Alright 👌🙂