The input library tracks available input devices, manages device state, and allows the session to register handlers for events.
The session creates an input pipeline that is configured for the specific product. First, the session decides which types of input devices the input pipeline should support. Then, the session registers input handlers for input events.
The input library provides implementations for common input handlers, such as Scenic and input method editors (IME). After the session instantiates components that consume input, the input pipeline directly sends input events to those components through the registered input handlers.
An input pipeline manages InputDeviceBinding
s and InputHandler
s.
InputDeviceBinding
represents a connection to a physical input device (e.g. mouse, keyboard).InputHandler
represents a client of InputEvent
s.An input pipeline routes input from physical devices to various clients by doing the following:
/dev/class/input-report
.InputEvent
s through InputHandler
s.Session authors are responsible for setting up input pipelines. More details on how can be found in input_pipeline.rs.
An InputDeviceBinding
does the following:
InputReport
file located at /dev/class/input-report/XXX
.InputEvent
s from the DeviceDescriptor
and incoming InputReport
s.The input pipeline creates and owns InputDeviceBinding
s as new input peripherals are connected to a device.
When an InputHandler
receives an InputEvent
, it does at least one of the following:
InputEvent
to the relevant client component.InputEvent
s for the next InputHandler
to process.InputHandler
s must satisfy at least one of these conditions, but otherwise their implementation details can vary.
The developer guide includes an example implementation of an InputHandler
.