[PATCH 02/11] Add libinput_device_has_key function

[Bill Spitzak]

On 11/06/2014 05:17 PM, Peter Hutterer wrote:
> On Thu, Nov 06, 2014 at 11:41:20AM -0800, Bill Spitzak wrote:
>> It sure seems like an api that returned a list of all the keycodes the
>> device has would be better. It looks like the client has to try every
>> possible keycode to find out what exists with this.
>
> what is the caller (which is not a wl client!) going to do with the list?

I'm mostly concerned that the api seems to be vastly different than the 
api for keyboards, even though both devices have multiple buttons.

I also have some doubts that devices are going to nicely use the desired 
single keycode for this function, and thus libinput users are going to 
be forced to try a whole set of keycodes to find the one that works.