Input Components Standard is developed to support adaptive control. It means that the Standard supports different input devices (namely keyboard, gamepad, mouse and touch screen). The Standard also supports dynamic configuration of control of external system of control settings. General workflow of standard looks as follows:
Control layout consists of arbitrary amount of control elements. First, control element calculates the states of every InputComponentController, then they are assembled into InputHubController, then, if necessary, common value is being adjusted by InputPostprocessController component and finally it goes to the external character control component.
InputComponentController class is the basis for all components of hardware input. Standard includes the minimum set of hardware input components, which could be conveniently classified into two groups: mechanical and touchscreen. Derivation tree looks as follows:
Descendants of InputComponentController class is responsible for bindings to buttons/ axis of the input device and the adjustment of different input parameters (e.g. sensitivity, inversion etc.). For example, MechanicalDirection2DController component, adjusted to recieve the input from gamepad, looks as follows:
InputHubController component is aggregator of all InputComponentController components for control element. As can be seen in general scheme, InputHubController supports up to four hardware control variations (i.e. keyboard, gamepad, mouse and touch screen). Depending on which InputComponentController component is active, InputHubController gets corresponding input data and defines input mode. If several InputComponentController components happen to be active, InputHubController chooses top-priority one, according to the determined order:
Apart from four references to input components of different devices, InputHubController also has property-enumeration inputMode, the value of which indicates the current active input device, as well as OnInputModeChanged event that is being triggered at the moment of switching the active input device. In Editor, InputHubController looks as follows: