Pointer motion events were already handled, it was just lacking the actual exposition to the API.
Oops, my rebase erased jadahl’s comment (and fixed the main issue).
Anyway, to answer that question, I think pointer events from outside of the window are very useful in some cases, think an OpenLayers-like map application, the user wants to be able to scroll even outside of the window, it makes a frustrating experience if the window is small and input stops at the edges of the window.
The comment is still there: linkmauve/glfw@be327a3
The wl_*.c part looks fine now. @elmindreda, can you confirm the change to input.c is correct and won't break other platforms?
@jadahl It's... tolerable. I'd rather it use platform local variables instead of re-introducing shared logic that will do nothing on any other platform.
If Mir works the same as Wayland then I guess this way is all right.
wayland: Implement glfwGetCursorPos
Addressed your issues, everything stays in the wl_* files now.
Merged. Thank you!