[AyanamiKaine]

Slightly related. On wayland based linux desktops this would never work because an app is not allowed to hijack the mouse pointer to dispatch events. I believe only the compositor is allowed to do that.

I know, because I wanted to automate a GUI task using PyAutoGUI and it wouldnt work on wayland no matter what.

[KetoManx64]

This is why I'm still on X11, the lack of deep level accessibility/automation is still a big hurdle when it comes to Wayland.

[AyanamiKaine]

Yea, one way I saw you can circumvent it is by running in xwayland mode. But that can come with its own problems.

[binarin]

Actual problem on Wayland is that it often doesn't work when you are trying to click somewhere in the menu - for the mouse clicking app to read keyboard input, it must take focus away from the app where the click should go. And some toolkits just close menus on focus loss.

I personally use wl-kbptr, and the problem above is the only one that can't be solved without explicit support from the compositor.

[AlienRobot]

I wonder if blender works on wayland, because it has a feature that makes the mouse cursor "loop" across the window if you are dragging something.

[AyanamiKaine]

That features works completly fine when I use Blender(5.2) and wayland cant say if older versions might not work.

[jcelerier]

The protocol for this has recently been accepted, now it has to be implemented by every compositor

[AlienRobot]

That sounds like hell. All this just to set the X, Y of the mouse pointer?

[jcelerier]

Not even, this was deemed too insecure. So now we have to have one protocol per-use case instead of something that allows to handle easily all the use cases we already know exist - the most stupid thing possible

[toast0]

> That sounds like hell.

Wayland isn't an eternal punishment, it's just a protocol. :p

[gen2brain]

What about wp_pointer_warp_v1? That should be supported in some compositors. But not sure how to actually "send" the click event.

I often try a session with Labwc/LxQt instead of my Openbox/LxQt, and while there is progress, still not fully usable, so still no Wayland for me. But with X11, I can at least add xvfb, xdotool, and other utils, and AI has no problem writing (and testing) a GUI for me.

[AyanamiKaine]

Oh wp_pointer_warp_v1 works fine when you want to move the cursor that is not a problem. One application can simply say move the mouse to a different window but it cannot say click.

So in the sense as far as I understand it is that in wayland one application is not allowed to use the input of IO devices to interact with other applications.

[gen2brain]

So, "security" strikes again. Windows shell not be moved, pointers shell not be clicked, but you can move the mouse if you want to.

[uukelele]

May I interest you in this:

https://github.com/uukelele/waydotool

[Fire-Dragon-DoL]

There is mouseless that seems to work on wayland

https://mouseless.click/

[AyanamiKaine]

But only if you "disable Wayland’s extra restrictions around keyboard/mouse access for Mouseless to work". [0]

[0] https://mouseless.click/docs/wayland_configuration.html

[kreelman]

That is an option, but it's not free.