[RFC libinput] Add dial input device support
prasannatsmkumar at gmail.com
Thu Feb 18 08:38:09 UTC 2016
Thanks for your time in looking at the patch.
> First: yes, implementing support for dial interfaces is within the scope of
> libinput, I think it makes sense to add this. But not quite in this form,
> the various CAP flags are libinput interfaces that denote a specific
> functionality. We should not add one per event group.
> A while ago we started work on the so-called buttonset interface which is
> a generic interface to support a bunch of devices like yours:
> Since that patchset we've split out the wacom-specific parts so you can
> ignore any strip/ring handling. There is no dial axis atm, but there
> could be.
> Have a look at that patchset, the documentation should explain what the
> interface is for, etc. I think adding dial to buttonset and then getting
> that interface ready for merging is the best approach here.
Thanks for the info. Could not find the buttonset interface patch in
master branch yet. Will use buttonset interface and provide a patch
once it is merged. Does that make sense?
> One comment on the API (to save you from scrolling down):
> libinput_event_dial_get_rotation_count() should simply be
> libinput_event_dial_get_rotation() and return the value in degrees. This is
> more flexible than the current one which reads like it's multiples of 360
Certainly not multiple of 360 degree, value need not be in degree.
Dial is relative and returns +1, +2 or -2.
Will change the API based on the buttonset interface API convention.
Thanks and regards,
More information about the wayland-devel