There’s no X WMs that fake input devices, or organise global hotkeys, or a thousand other things people always quote when bashing wayland. You can get bog-standard X applications which do that because X has literally no security model, but the feature set between e.g. KDE on X and KDE on wayland is virtually identical.
It’s like you want to misunderstand me. I’m not bashing Wayland. That part of my comment isn’t about WMs and compositors. It’s about how hard it is to make macro that does a few clicks and types a few keys into an app etc… It’s still very hard in Wayland. I’m sure it will get better some day, but we’re not there yet.
There’s no X WMs that fake input devices, or organise global hotkeys, or a thousand other things people always quote when bashing wayland. You can get bog-standard X applications which do that because X has literally no security model, but the feature set between e.g. KDE on X and KDE on wayland is virtually identical.
It’s like you want to misunderstand me. I’m not bashing Wayland. That part of my comment isn’t about WMs and compositors. It’s about how hard it is to make macro that does a few clicks and types a few keys into an app etc… It’s still very hard in Wayland. I’m sure it will get better some day, but we’re not there yet.
Have a look here. Not sure how they do it the proper way would be to run the desktop environment as a subcompositor of autokey.
Meanwhile, though, do try CLI automation. It’s the Unix way.