Changes between Initial Version and Version 1 of Ticket #1066, comment 3


Ignore:
Timestamp:
May 25, 2014, 4:01:53 AM (10 years ago)
Author:
historic_bruno

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1066, comment 3

    initial v1  
    1 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.
     1One 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.
    22
    3 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 showings its accelerator keys).
     3A 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).