New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mac OS X Menus & Command key #135
Comments
From davidcapello on June 24, 2014 19:37:02 Status: Accepted |
From davidcapello on August 04, 2014 05:26:28 Issue #437 has been merged into this issue. |
From davidcapello on August 05, 2014 16:19:18 Labels: OS-MacOSX |
From davidcapello on August 05, 2014 20:43:48 The command key support was added. Now all shortcuts with Ctrl+char were converted to Cmd+char in Mac OS X platform. |
From davidcapello on August 09, 2014 14:09:39 Each element can contain a shortcut="..." attribute and other attributes for platform specific variants if they're preferred: |
This change should be reverted in some way when the OS X menus are implemented (issue #135)
OS X menus will be added in v1.1. |
You probably already have this prioritized, but as a long-time Mac user, native menus are not even on my radar for Aseprite feature requests. The current UI is charming! |
@irskep actually the menu is not as important as another feature (that requires the menu): So implementing ⌘H and ⌘M requires the native menu, and something nice would have the entire menu available in the top bar (and options to show/hide the pixel art UI menu). |
From davidcapello on July 11, 2012 13:42:39
Mac OS X should show the menus at the top bar and the keyboard shortcuts should use the command key instead of ctrl (or both variations).
Original issue: http://code.google.com/p/aseprite/issues/detail?id=135
The text was updated successfully, but these errors were encountered: