Question about wl_pointer_set_cursor and hotspots
waris.boonyasiriwat at gmail.com
Wed Jan 6 20:03:42 UTC 2021
Sorry if this is not the right place as this is the first time I use
Earlier this year I raised an issue against a UI framework GLFW where the
cursor hotspot does not seem to be respected in wayland:
However, upon further digging, a GLFW developer (and later myself) seem to
have confirmed that GLFW is sending the correct cursor information to the
compositor. The source code for the cursor call is found here:
I have tried changing the hotspot to nonsensical numbers such as 0,0 or
100,100, but I noticed no change in behaviour at all. The hotspot always
appears to be at the top left.
I have noticed this behaviour on two separate compositor implementations:
weston and mutter. This led me to consult this mailing list, to see whether
we are misusing the API somehow?
Your help is much appreciated.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the wayland-devel