protocol: spell out that we're using linux/input-event-codes.h button codes
Because we already rely on it in the callers anyway. This is a retrofit, which
is not ideal but I'm not sure any compositor out there uses anything else.
Might as well define it.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Reviewed-by: Jonas Ã…dahl <jadahl@gmail.com>
Reviewed-by: Daniel Stone <daniels@collabora.com>
Peter Hutterer authored 7 years ago
Daniel Stone committed 7 years ago
1871 | 1871 | enter event. |
1872 | 1872 | The time argument is a timestamp with millisecond |
1873 | 1873 | granularity, with an undefined base. |
1874 | ||
1875 | The button is a button code as defined in the Linux kernel's | |
1876 | linux/input-event-codes.h header file, e.g. BTN_LEFT. | |
1877 | ||
1878 | Any 16-bit button code value is reserved for future additions to the | |
1879 | kernel's event code list. All other button codes above 0xFFFF are | |
1880 | currently undefined but may be used in future versions of this | |
1881 | protocol. | |
1874 | 1882 | </description> |
1875 | 1883 | <arg name="serial" type="uint" summary="serial number of the button event"/> |
1876 | 1884 | <arg name="time" type="uint" summary="timestamp with millisecond granularity"/> |