The input pipeline library tracks available input devices, manages device state, and allows the session to register handlers for events.
An input pipeline runs alongside session. It is preconfigured to support a set of input devices. This will be configurable by the session in the future.
The input pipeline 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.
InputDeviceBindingrepresents a connection to a physical input device (e.g. mouse, keyboard).
InputHandlerrepresents a client of InputEvents .
An input pipeline routes input from physical devices to various clients by doing the following:
- Detects and binds to new input devices as they appear in
Session authors are responsible for setting up input pipelines. More details on how can be found in input_pipeline.rs.
InputDeviceBinding does the following:
- Connects to an
file located at
InputEvents from the InputDeviceDescriptor and incoming
The input pipeline creates and owns
InputDeviceBindings as new input
peripherals are connected to a device.
InputHandler receives an
InputEvent, it does at least one of the
- Forwards the
InputEventto the relevant client component.
- Outputs a vector of
InputEvents for the next
InputHandlers must satisfy at least one of these conditions, but otherwise
their implementation details can vary.
The developer guide includes an
example implementation of an
InputDeviceBinding : /docs/glossary/README.md#InputDeviceBinding InputHandler : /docs/glossary/README.md#InputHandler InputEvent : /docs/glossary/README.md#InputEvent InputReport : /docs/glossary/README.md#InputReport InputDeviceDescriptor : /docs/glossary/README.md#InputDeviceDescriptor