In Chapter 4 we laid the groundwork for better understanding the Unity Event System and its integration with VRTK. For me, it’s helpful to think of events as messages sent between classes and objects to notify different components of a program that a change has occurred. Because user input into our VR applications alters the state of the program, it, too, is an event. As an event, user input fits nicely into the list of responsibilities handled by VRTK as an interface for the Unity Event System.
Traditionally, in platforms such as web development, user input has taken the form of keyboard ...
