Skip to content
This repository was archived by the owner on Sep 2, 2021. It is now read-only.

Conversation

@RaymondLim
Copy link
Contributor

This fixes issue adobe/brackets#10249.

@redmunds redmunds self-assigned this Dec 21, 2014
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rlim Why can't the new keys be defined using same pattern as existing keys? For example:

    const ExtensionString pageUp    = (ExtensionString() += NSPageUpFunctionKey);

Seems simpler and more consistent.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@redmunds Because they're unichar and we need to convert them to UTF8. Otherwise, you will see a different character show up in the menu. e.g. PageUp shows up as a comma

@redmunds
Copy link
Contributor

@rlim Done with code review. Works great. Just 1 comment.

@redmunds
Copy link
Contributor

Looks good. Merging.

redmunds added a commit that referenced this pull request Jan 16, 2015
Support more common key names in native menus
@redmunds redmunds merged commit 031f9ad into master Jan 16, 2015
@redmunds redmunds deleted the rlim/support-more-key-names branch January 16, 2015 18:52
redmunds added a commit that referenced this pull request Dec 8, 2015
Support more common key names in native menus
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants