Re: key equivalents question
Re: key equivalents question
- Subject: Re: key equivalents question
- From: Jerry Krinock <email@hidden>
- Date: Fri, 01 Jul 2011 22:09:45 -0700
On 2011 Jul 01, at 17:12, Brian Gardner wrote:
> Is there something that I need to do, in addition to
> setting the key equivalent in Interface Builder?
No.
> And why does that work for some choices of keys but not other choices?
The short answer is: that's the way it is, and you need to restrict yourself to key equivalents that work.
Here's a longer answer, which probably has some errors which someone will please correct.
Some key equivalents are handled by prior objects in the responder chain, or trapped by lower levels of the system.
• ⌘space is swallowed by Spotlight.
• ⌘F may be swallowed by a text view, to Find text. Look in the Edit menu and see if ⌘F is assigned there.
• I think that ⌥-anything is swallowed by the text input system, for alternate characters. For example, when I type ⌥F I get the character ƒ.
Does anyone know a document sets forth all the restrictions?
I know that some apps override the restrictions. For example, LaunchBar hijacks ⌘space from Spotlight and QuicKeys can assign shortcuts to ⌥whatever. Does anyone know how they do that?
Some of the answers may be in here:
http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/EventOverview/EventArchitecture/EventArchitecture.html#//apple_ref/doc/uid/10000060i-CH3-SW10
although they seem to concentrate mostly on what happens assuming that the key event makes it to your app.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden