-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wayland mouse movement #14
Comments
AFAIK AT-SPI does not fully support wayland either. At least synthesizing mouse events it a problem because of the way the clients interact with compositor. There is some major work on the GNOME project side though. You can check here for details https://wiki.gnome.org/Accessibility/Wayland |
Thanks for the link, indeed I am generally interested in remote control for Wayland… And I don't know what "AT-SPI" is, FWIW… |
AT is Accessibility Tools like screen readers, but also interfacing with input devices like a mouse. SPI is service programmable interface, or something like that. This is the big blocker here, I think: |
The official KDE Connect has problems with Wayland currently, so one cannot move the mouse when trying to remote control it via the phone.
I can click and use keyboard input, but moving the cursor does not work.
So what about your version? As it seems to be written for GNOME mainly, and GNOME makes use of Wayland quite often and has a good compatibility, this feature should be added here, too.
The text was updated successfully, but these errors were encountered: