Re: [RFC libinput] Add dial input device support

2016-02-21 Thread PrasannaKumar Muralidharan
> remember that libinput is a low-level library and doesn't know about how a > specific device is being used by the layers above it. Hence a value in > degrees isn't any less useful than a value in miscellaneous units which is > what the _discrete() API bit is for. If the caller cares about units,

Re: [RFC libinput] Add dial input device support

2016-02-19 Thread Peter Hutterer
On Fri, Feb 19, 2016 at 08:03:52PM +0530, PrasannaKumar Muralidharan wrote: > > right. the approach we used for this was to have an API that exports the > > value in degrees and an API for get_value_discrete() or similarly named. > > Look up the libinput_event_pointer*axis* API to get an idea. > >

Re: [RFC libinput] Add dial input device support

2016-02-19 Thread PrasannaKumar Muralidharan
> right. the approach we used for this was to have an API that exports the > value in degrees and an API for get_value_discrete() or similarly named. > Look up the libinput_event_pointer*axis* API to get an idea. For several devices (example dimmers used for controlling lamps) value in degrees is

Re: [RFC libinput] Add dial input device support

2016-02-19 Thread PrasannaKumar Muralidharan
Hi Andreas, > Instead of car steering wheels I would rather mention rotaty knobs that are > common in car infotainment systems to navigate through menues. Those are > relative - you never get absolute angles just rotation ticks. > But is that the type of device you had in mind? Those devices usua

Re: [RFC libinput] Add dial input device support

2016-02-18 Thread Peter Hutterer
On Thu, Feb 18, 2016 at 02:08:09PM +0530, PrasannaKumar Muralidharan wrote: > Hi Peter, > > 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,

Re: [RFC libinput] Add dial input device support

2016-02-18 Thread Andreas Pokorny
Hi, On Mon, Feb 15, 2016 at 11:51 AM, PrasannaKumar Muralidharan < prasannatsmku...@gmail.com> wrote: > From: PrasannaKumar Muralidharan > > I am implementing dial input device support and would like to get feedback > on the code that I have implemented so far. Did not implement test cases as >

Re: [RFC libinput] Add dial input device support

2016-02-18 Thread PrasannaKumar Muralidharan
Hi Peter, 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.

Re: [RFC libinput] Add dial input device support

2016-02-17 Thread Peter Hutterer
Hi PrasannaKumar On Mon, Feb 15, 2016 at 04:21:23PM +0530, PrasannaKumar Muralidharan wrote: > From: PrasannaKumar Muralidharan > > I am implementing dial input device support and would like to get feedback > on the code that I have implemented so far. Did not implement test cases > as of now, a

[RFC libinput] Add dial input device support

2016-02-15 Thread PrasannaKumar Muralidharan
From: PrasannaKumar Muralidharan I am implementing dial input device support and would like to get feedback on the code that I have implemented so far. Did not implement test cases as of now, any pointers on how the test framework works will be helpful. Smartwatch can use dial input, Car can u