Collaboration diagram for devices:
Of course Keyboard and Mouse but you can also handle haptic devices like VTPlayer or FF3D ForceFeeback device configured in ReachinAPI. All devices classes was separated in three parts. Input/Ouput and Sender. All agents named sender send devices state information on the bus. For example the KeyboardSenderAgent sends the key pressed and released. These agents have no bind on the bus but "quit".
Agents named input will catch generic messages from sender agents. Input agents are helpers for developers: they bind "standard messages" from the related sender agent. To help development, we highly recommend to inherit the corresponding input agent when we want informations from a device.
Output agents handle messages to render incoming informations on the output devices.
Modules | |
ForceFeedBack 3d Device | |
classes grouping all FF3D Device control classes | |
VTPlayer device | |
classes grouping all VTPlayer control classes | |
Keyboard | |
Keyboard control classes. | |
Mouse | |
Mouse control classes. |