Interface for button requests and events. This interface
is available on devices with the ei_device.capability button.
Interface for ensuring a roundtrip to the EIS implementation.
Clients can handle the ‘done’ event to get notified when
the related request that created the ei_callback object is done.
The core connection object. This is the top-level object for any communication
with the EIS implementation.
An ei_device represents a single logical input devices. Like physical input devices
an ei_device may have multiple capabilities and may e.g. function as pointer
and keyboard.
This is a special interface to setup the client as seen by the EIS
implementation. The object for this interface has the fixed object
id 0 and only exists until the connection has been set up, see the
ei_handshake.connection event.
Interface for keyboard requests and events. This interface
is available on devices with the ei_device.capability keyboard.
Interface for ensuring a roundtrip to the client implementation.
This interface is identical to ei_callback but is intended for
the EIS implementation to enforce a roundtrip to the client.
Interface for pointer motion requests and events. This interface
is available on devices with the ei_device.capability pointer.
Interface for absolute pointer requests and events. This interface
is available on devices with the ei_device.capability pointer_absolute.
Interface for scroll requests and events. This interface
is available on devices with the ei_device.capability scroll.
An ei_seat represents a set of input devices that logically belong together. In most
cases only one seat is present and all input devices on that seat share the same
pointer and keyboard focus.
Interface for touchscreen requests and events. This interface
is available on devices with the ei_device.capability touchscreen.