Fusuma VS ydotool

I don't think there are native gestures in qtile. I use fusuma, since it works better for me on X11 and wayland, but I've also used libinput-gestures in the past when on X11, and that works too.

I'm new to linux, running last version of ubuntu MATE. Tried to get fusuma to have a better experience with my touchpad (I'm using hp notebook). I followed the whole guide for ubuntu on the Github page, created the config.yml using these two commands:

For info, I've been using Fusuma to configure my touchpad gestures and it is awesome!

https://github.com/iberianpig/fusuma this might do the job? I have been using it on Hyprland and, despite the downside of being in Ruby, it works really well and seems stable.

I use Fusuma to manage gestures and have deactivated the COSMIC gestures extension.

The gestures are interpretations of the touch signals that the trackpad provides, and those signals are available to your computer. The gestures and their functions are features of the operating system, but you can define your own gesture with tools like https://github.com/iberianpig/fusuma. Are you mad that the Magic Trackpad does not come with a full set of gesture support for Mint, Gnome, i3, or any of the gosh hundreds of window managers out there? What would you expect to happen to resolve this complaint?

I like using fusuma.

Thx! I actually looked at this, but it only can emulate shortcuts pressing, as I get it. Instead I tried https://github.com/iberianpig/fusuma which has more features and works perfectly with Hyprland.

I use Fusuma to configure my gestures and it is awesome!

you can install fusuma (https://github.com/iberianpig/fusuma) and add their i3 config (https://github.com/iberianpig/fusuma/wiki/i3) for a start

Wayland provides little by design, so this is quite typical. For example:

Screensharing is handled by pipewire [0], changing keyboard layouts aren't defined [1] by wayland, and generally anything Wayland devs think would 'corrupt' their protocol.

They leave most things to the compositor to implement, which leads to significant fragmentation as every compositor implements it differently.

Long gone are the days of xset and xdotool working across nearly every distro due to a common base, now the best you'll get is running a daemon as root to directly access `/dev/uinput` [2] or implementing each compositors accessibility settings (if they have them) as a workaround.

[0] https://superuser.com/questions/1221333/screensharing-under-...

[1] https://unix.stackexchange.com/questions/292868/how-to-custo...

[2] https://github.com/ReimuNotMoe/ydotool

I personally use libinput-gestures to call commands using touchpad gestures. You can also combine it with ydotool to bind macros and such to your gestures, e.g. 4 fingers swipe down closes the current window, 3 fingers swipe left or right changes workspace, etc

Have you tried using the systemd unit file supplied with ydotool? It's probably installed somewhere on your system. Else you can get it here and just change the install location of ydotoold.

For simulated keyboard there are tools such as dotool or ydotool and KeePass extensions such as KPUInput that work by giving the user access to /dev/uinput. That works, but it's a bit inelegant; I guess in the future a Wayland protocol for simulated keyboard input will emerge, like wlroots already has, also for virtual pointers.

ydotool is the generic equivalent. It works on both X11 and Wayland environments.

Autokey does not work yet, but there is Hawck and Espanso that you could play around with. And there is ydotool if all you need is simulating basic input (as in ydotool mousemove -x -10 -y -10, ydotool type 'Hello world!' and so on).

Does ydotool do what you need? I haven't even tried Wayland in years. I'm sure someday I'll find the need.