Changeset 2907 for code/branches/questsystem5/src/core/input/KeyBinder.cc
- Timestamp:
- Apr 8, 2009, 12:36:08 AM (15 years ago)
- Location:
- code/branches/questsystem5
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
code/branches/questsystem5
- Property svn:mergeinfo changed
-
code/branches/questsystem5/src/core/input/KeyBinder.cc
r2713 r2907 42 42 #include "core/CoreIncludes.h" 43 43 #include "core/ConfigFileManager.h" 44 #include "core/Core.h"45 44 #include "InputCommands.h" 46 45 #include "InputManager.h" … … 309 308 } 310 309 311 void KeyBinder:: tickMouse(float dt)310 void KeyBinder::updateMouse(float dt) 312 311 { 313 312 if (bDeriveMouseInput_) … … 349 348 // Why dividing relative value by dt? The reason lies in the simple fact, that when you 350 349 // press a button that has relative movement, that value has to be multiplied by dt to be 351 // frame rate independent. This can easily (and only) be done in tickInput(float).350 // frame rate independent. This can easily (and only) be done in updateInput(float). 352 351 // Hence we need to divide by dt here for the mouse to compensate, because the relative 353 352 // move movements have nothing to do with dt. … … 362 361 } 363 362 364 void KeyBinder:: tickJoyStick(float dt, unsigned int joyStick)363 void KeyBinder::updateJoyStick(float dt, unsigned int joyStick) 365 364 { 366 365 for (unsigned int i = 0; i < JoyStickAxisCode::numberOfAxes * 2; i++)
Note: See TracChangeset
for help on using the changeset viewer.