libei 1.0 Nears For Emulated Input On Wayland

[phoronix]

Phoronix: libei 1.0 Nears For Emulated Input On Wayland

Libei has been the multi-year effort by Red Hat's leading input expert Peter Hutterer on

https://www.phoronix.com/news/libei-1.0-RC

[spyke]

I see in the description that this is what Synergy/Barrier/InputLeap needs for Wayland. Is anyone aware if one of these apps is working on integrating `libei`?

[emansom]

How does this compare to the kernel module uinput?

[spyke]

How does this compare to the kernel module uinput?

From `waynergy` project page:

uinput (everyone else)
First and foremost it should be kept in mind that kernel-level virtual input may have undesirable side effects because the compositor is being completely bypassed. This most notably means that virtual consoles are no longer isolated as far as input is concerned, so simple lock screens can be easily bypassed if more than one session is active.

[Myownfriend]

The article says this is Wayland focused but wouldn't this primarily interact with libinput which is used by Xorg as well?

[stompcrash]

Would this allow someone to write a program that could send repeated key or button presses for games which do not do autofire? Or send mouse movements to compensate for gun recoil in FPS games?

[Quackdoc]

this is great, on the waydroid side of things, we desperately need touchscreen emulation programs the only thing we are now missing is being able to create overlays universally. although that isn't strictly necessary for a lot of the functions input mappers can do.

there are a lot of possibilities here, stylus+pressure emulation for artists could be very cool for instance

Would this allow someone to write a program that could send repeated key or button presses for games which do not do autofire? Or send mouse movements to compensate for gun recoil in FPS games?

I dont know the current extent of it, but this would be something covered in it's usecase

[oiaohm]

Would this allow someone to write a program that could send repeated key or button presses for games which do not do autofire? Or send mouse movements to compensate for gun recoil in FPS games?

https://github.com/werpu/input_pipe

https://github.com/snyball/hawck

Parties already can do that using python/Lua... and the uinput system of the Linux kernel. Yes uinput system allows you to fake up full input devices.

So the functionality you are talking about all libei changes is
1) libei prevents the infinity loop problem with a key generated by libei cannot go into the input of the wayland application providing that libei instruction to generate it.
2) not needing as high of privilege.

[mazumoto]

Seriously? libicecream and libegg connected through mush?

[darkdragon-001]

Here is a tracking issue to follow the implementation into various components: https://gitlab.freedesktop.org/libin...bei/-/issues/1

I see in the description that this is what Synergy/Barrier/InputLeap needs for Wayland. Is anyone aware if one of these apps is working on integrating `libei`?

input-leap support has already been merged and tested some time ago (https://github.com/input-leap/input-leap/pull/1594), but still requires custom builds of wayland compositor and portals.