Fix hotkeys in Atlas

[Aviv]

There are several problems with hotkeys in Atlas.

It's impossible to use any of the movement keys (WASD...) in chat. Making the use of most cheats impossible (because they contain these letters), while some of the cheats would be very handy in Atlas.

It doesn't recognise the ALT modifier. So ALT+D (open developer overlay) is recognised as D (move right). And there's no way left to open the developer overlay since r15205.

Camera rotation with Q and E keys turns the other way around.

Changing building rotation hotkeys works ingame but not in Atlas. Described here: ​http://twitter.com/#!/FlorianJW/status/149980476650692608

[historic_bruno]

We really need to share hotkeys between Atlas and the game, as much as possible.

[historic_bruno]

One problem is that there will be conflicting hotkeys in Atlas UI (e.g. Alt+F to open the file menu), and users want to type or use the keyboard to change the various editor options, without them always being captured by the game view. Basing this on mouse position or focus alone may not be enough, it's aggravating if the mouse moves slightly and suddenly the user can't finish their map description.

A possible solution is to let the game view capture more of the keyboard events in "simulation test" mode, as typically that's what the user wants (with the previous example, Alt+F could toggle framerate display, instead of opening the file menu). Right now, I think the Atlas UI always has priority on handling the keyboard inputs (where "handled" might be something like the menu bar showing its accelerator keys when Alt is pressed).

[sanderd17]

Switching the hotkey sets on focus change isn't very good indeed, but it can be switched when the simulation is started, or when the game pointer tool is selected (the mouse tool that lets you modify the simulation, but not the map directly). Both sound reasonable for me.

[leper]

In 15466:

Change camera rotation in Atlas to be the same as in the game. Refs #1066.

[otero]

I've studied this problem and I found the reason this problem is arising, but solving this problem may require a mayor refactorization of the atlas code. I don't have problem in making the required changes, but I would like to ask before if there is no problem in the refactorization part or if I should "hack" a solution good enough just to fix this problem. There is a chance that I could make the Atlas code a little simpler and cleaner and maybe fix some other ticket in the process.

[Stan]

Before you do so you might want to look at trompetin17 atlas branch on github. Herewrote parts of the UI