How Wayland manages the automation/access of input devices and deal with block on them

[Pekka Paalanen]

On Fri, 25 Nov 2022 07:04:14 +0000
"Victor Borghi Gimenez (FIPT)" <victorborghi at ipt.br> wrote:

> Hello there,
> 
> I was developing some scripts to automate test cases using Xlib
> package in Python to test resources (click in icons, verify the
> opened window, text that appeared) on a new linux distro here, before
> it was standardized in X11 and now they decided to standardize it in
> Wayland and it let me stucked to keep the development of the scripts
> because the lack of working. I also give a dig to find packages in
> Python and mouse/keyboard simulation tools compatible with Wayland
> which work in terminal and I found python-uinput which works for
> simulation of keyboard but not to simulate mouse, and ydotool which
> gave me error. Now I would like to know how Wayland manages the
> automation of mouse and keyboard opposed to X11/XOrg in order to
> develop any script in Python or other language to automate input
> devices, I don't have any knowledge of the differences from XOrg and
> Wayland and I fell in this study because the need to automate Wayland.

Sorry, Wayland does not standardise that yet.

Is your aim to test applications or Wayland compositors?

If you want to test applications, you might be able to build something
against a specific Wayland compositor or a compositor library.

The only truly generic interface is uinput (Linux kernel evdev), and
using that requires root privileges and comes with a bunch of caveats.

Another generic approach is libei, but it requires explicit integration
in compositors, and I'm not aware of any compositor doing that yet:
https://gitlab.freedesktop.org/libinput/libei

Finally, each compositor might have something of its own, or not.


Thanks,
pq
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.freedesktop.org/archives/wayland-devel/attachments/20221128/2fac8920/attachment.sig>