Make the button events carry event codes, not indices

Brings this more in line with libinput and, well, everything on linux, really.

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
This commit is contained in:
Peter Hutterer 2020-08-03 20:46:13 +10:00
parent 39fcf16ec8
commit cb192945d2
2 changed files with 3 additions and 5 deletions

View file

@ -392,11 +392,9 @@ ei_device_pointer_motion_absolute(struct ei_device *device,
* the @ref EI_DEVICE_CAP_POINTER_ABSOLUTE or
* @ref EI_DEVICE_CAP_POINTER capability.
*
* Buttons are merely sequentially numbered. It is up to the server to map
* button numbers into semantic button codes (if any). A server may silently
* ignore button events outside meaningful ranges.
* Button codes must match the #defines in linux/input-event-codes.h
*
* @param button A sequentially numbered button, starting at index 1
* @param button The button code
* @param is_press true for button press, false for button release
*/
void

View file

@ -419,7 +419,7 @@ eis_event_pointer_get_absolute_y(struct eis_event_pointer *ptrev);
/**
* For an event of type @ref EIS_EVENT_POINTER_BUTTON return the button
* index (starting at 1).
* code as defined in linux/input-event-codes.h
*/
uint32_t
eis_event_pointer_get_button(struct eis_event_pointer *ptrev);