You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Moving the level editor's viewpoint diagonally via WASD is only possible if W (up) or S (down) is pressed, THEN the left/right key. However, pressing A (left) or D (right) BEFORE W or S negates the up/down movement.
Not a big deal but it makes the level editor movement feel "glitchy."
watusimoto, this is because we're testing for input strings instead of input codes in EditorUserInterface::onKeyDown(). When pressing 'A' + 'S', the inputString returned is just 'A' (see diagnostics).
The solution is to test for input codes again. What was the reason for moving to input strings in the first place? I don't remember..
Correct diagnosis, but wrong solution, as raw input codes cannot differentiate between Up and Shift+Up (for example). The solution I implemented looks at what keys you've most recently pressed, and selects that one if more than one key is pressed. Previously, we focused on an arbitrary key.
From Jomskylark on December 19, 2012 19:12:05
Moving the level editor's viewpoint diagonally via WASD is only possible if W (up) or S (down) is pressed, THEN the left/right key. However, pressing A (left) or D (right) BEFORE W or S negates the up/down movement.
Not a big deal but it makes the level editor movement feel "glitchy."
Original issue: http://code.google.com/p/bitfighter/issues/detail?id=187
The text was updated successfully, but these errors were encountered: