libinput: automatic device discovery

[Johennes]

I'm working on an application that is meant to be run on many different types of devices which means I can't hard-code the /dev/input/event... paths because I don't know them at build time. It would be great if the libinput driver could provide an interface for automatically detecting touchscreens, pointer devices and keyboards.

I have some very rudimentary code here that basically just walks the /dev/input/event... files, makes a libinput call to determine the device capabilities and then filters the files based on that.

I'd be interested to know if you would consider adding something like this to lv_drivers? I think this could be beneficial to other users as well.

[kisvegabor]

What if you simply do #define LIBINPUT_NAME my_find_input_dev()?

Anyway, I believe it'd be useful to add libinput_find_touch_dev(), libinput_find_mose_dev(), etc to libinput.c so that the user could use them as LIBINPUT_NAME.

Probably we'd need LIBINPUT_TOUCH_NAME, LIBINPUT_MOUSE_NAME, etc.

What do you think?

[Johennes]

Yeah, this overlaps a little with #151.

Using it directly in the config file is an interesting idea! The functions I'm using so far return all devices of a certain type. We could maybe wrap them in another set of functions to return only the first device of a type, that shouldn't be too complicated.

[kisvegabor]

Using it directly in the config file is an interesting idea! The functions I'm using so far return all devices of a certain type. We could maybe wrap them in another set of functions to return only the first device of a type, that shouldn't be too complicated.

Based on my last comment in #151, I think it'd be the approach now.