Peter Hutterer faa9500afe Add concept of active/passive libei contexts ... A libei context can be initialized as active or passive context - an "active" context sends events, a "passive" context receives events. The EIS context supports both simultaneously, it is up to the implementation to disconnect libei clients that it does not want to suppport. For example, the xdotool use-case creates an active libei context. The EIS implementation controls and sets up the devices, but libei sends the events. In an input-capturing use-case, the EIS implementation controls and sets up the devices **and** sends the events. libei is merely the receiver for any event, it cannot send events. Thus this use-case requires a passive libei context. Most of this code is copy/paste with minor modifications - libei already had the code to send events, libeis had the code to receive events, so the vast majority of this patch is copying the code into the respective other library, swap "ei" and "eis" and then apply the various minor modifications needed to hook into the existing library. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>		2022-03-04 14:04:33 +10:00
..
ei.proto	Add concept of active/passive libei contexts	2022-03-04 14:04:33 +10:00
meson.build	Replace the custom message parsing with protobuf	2020-07-31 13:05:11 +10:00