Changes between Version 3 and Version 4 of code/doc/InputManager
- Timestamp:
- Sep 18, 2008, 10:24:25 PM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
code/doc/InputManager
v3 v4 23 23 This state is always active after the InputManager has been created. It can be used to log input for instance if that is desired. The main purpose however is to reserve certain keys that always have a function, like the key to open the console. In order to realise that, a KeyBinder is used. 24 24 25 === Input Events === 26 OIS makes it simple and raises an event for every pressed or released button or key and for every axis that has moved. However, sometimes it would be a lot easier to only handle the active state. For instance simple movements can be achieved by accelerating as long as the user holds a key. To realise that, the InputManager generates an event of its own: keyHeld. It gets raised every tick whenever a button or key is held. Be careful to consider that the tick frequency varies! 27 25 28 == Initialisation, Destruction and Reloading == 26 29 The InputManager initialises the OIS library and sets up some basic input states like a Detector to run-time detect key names in the console, a joystick calibrator, a master state (see above) and an empty state for internal reasons.[[br]]