Wayland Relative Pointer API Progress

Steven Newbury steve at snewbury.org.uk
Sun Apr 19 04:45:09 PDT 2015

On Sun, 2015-04-19 at 15:29 +0900, x414e54 wrote:
> The way todo this seems to be for the compositor and client to 
> negotiate an event type they both can understand such as
> libinput_event or hid events and then a way to request a revokable 
> fd to the evdev directly so it can control LEDS and force feedback 
> etc. This allows for applications and compositors to grow separately 
> of the wayland protocol so it does not need updating every time 
> someone invents some new mouse device which needs 128bit integers 
> instead of doubles, has a z axis, thumbstick or tiny projector built 
> in, etc.

There's also the point that nothing stops games or sdl-like layers 
from using libinput to interpret the evdev stream, there's no need to 
keep re-implementing device handlers for each client, that way new 
devices supported by Wayland are automaticaly supported.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part
URL: <http://lists.freedesktop.org/archives/wayland-devel/attachments/20150419/65c5dac2/attachment-0001.sig>

More information about the wayland-devel mailing list