Re: 10.5 Only: If I say NO, NSOutlineView ignores cmd key, does its own thing
Re: 10.5 Only: If I say NO, NSOutlineView ignores cmd key, does its own thing
- Subject: Re: 10.5 Only: If I say NO, NSOutlineView ignores cmd key, does its own thing
- From: Jerry Krinock <email@hidden>
- Date: Wed, 4 Jun 2008 15:37:17 -0700
On 2008 Jun, 04, at 14:53, Corbin Dunn wrote:
http://developer.apple.com/releasenotes/Cocoa/AppKit.html#NSMenu
Disabled key equivalents passed throughPrior to Leopard, key
equivalents corresponding to disabled menu items would be ignored.
In Leopard, your application now has a chance to handle these. For
example, a key equivalent for control-K on a disabled menu item....
Thank you, Corbin. I understand the pass-through now, but I still
have an issue:
"cmd+upArrow" != "upArrow"
When I type cmd-upArrow, and myAction is disabled, the NSOutlineView
executes the action (moving the selection up) which I thought was
assigned to upArrow.
This seems to be incorrect, unless BOTH keyboard equivalents upArrow
^and^ cmd+upArrow are assigned to NSTable/OutlineView's
"moveSelectionUp" action. I'm not sure, because I cannot find any
documentation on precisely what are keyboard equivalents in NSTable/
OutlineView. I realize that upArrow is not really a keyboard
equivalent, more an over-ride of -keyDown, but the idea is the same.
Jerry
_______________________________________________
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