> Windows used to do this and it is completely nuts. They fixed it in recent
> versions
I don't know what version of Windows you're using, but I can still
observe this behavior in the Windows 8 file dialogs. I wrote a program
to work around it: https://github.com/madewokherd/xscrollwheel
Some to
> When the client receives a mouse-down event, it knows it is in this mode.
> The mode is exited when all the mouse buttons are released.
>
> While in this mode the mouse position is reported as though the user is
> dragging over a very large torus surface (ie it wraps at very large
> integers), th
> wl_pointer::enter event carries x,y, so even for relative pointer
> mode, it can tell at which point on the surface the pointer comes in.
> After that, the application can accumulate relative events to know the
> position inside the surface.
>
> Except that won't really work. I believe the relati
> Yup, good points here. I think we could reuse the wl_pointer
> interface, but just send relative motion in the motion event and it
> should go throught the wl_seat capability feature as Daniel describes.
With this approach, is it going to be possible to know both the
relative motion for an even
