Skip to content
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

Open
rugk opened this issue Aug 21, 2017 · 3 comments
Open

Wayland mouse movement #14

rugk opened this issue Aug 21, 2017 · 3 comments

Comments

@rugk
Copy link

rugk commented Aug 21, 2017

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.

@bboozzoo
Copy link
Owner

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

@rugk
Copy link
Author

rugk commented Aug 30, 2017

Thanks for the link, indeed I am generally interested in remote control for Wayland…

And I don't know what "AT-SPI" is, FWIW…

@andyholmes
Copy link
Contributor

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:

Bug 709999 - Wayland: Mouse event synthesis is not working

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants