Xcode-beta (8S201h): Xcode Extensions Cannot Provide Default Key Bindings

Originator:designatednerd
Number:rdar://28170032 Date Originated:06-Sep-2016 02:49 PM
Status:Closed Resolved:Duplicate
Product:Developer Tools Product Version:Xcode-beta (8S201h)
Classification:UI/Usability Reproducible:Always
 
Summary:
Xcode 8 extensions are not able to provide default key bindings for invocation

Steps to Reproduce:
- Build an xcode source editor extension
- Try to figure out how to set a default key binding for users to invoke the extension
- Fail to find API for this
- Note that in WWDC video it appears users must set key bindings on each plugin

Expected Results:
- Developers can provide a default key binding for an applicaiton

Actual Results:
- Users must set key bindings for each source editor extension they use manually. 

Regression:
(not a regression, this is a new feature)

Notes:
My guess is this was implemented to prevent potential collisions of key bindings, but I think it would probably be easier for users to allow developers to set a default key binding, then present the user with a dialog to resolve any conflicts between default key bindings. In most cases the key bindings should be reasonably different, and the user would easily be able to update or ignore the key binding for any given extension.

Comments

Received September 12th: "Engineering has determined that your bug report (28170032) is a duplicate of another issue (26900087) and will be closed."

By designatednerd at Sept. 15, 2016, 1:57 p.m. (reply...)

Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!