• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: [IB] - can't assign keyboard shortcut to a menu item
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [IB] - can't assign keyboard shortcut to a menu item


  • Subject: Re: [IB] - can't assign keyboard shortcut to a menu item
  • From: Graham Cox <email@hidden>
  • Date: Mon, 3 Aug 2009 23:00:08 +1000


On 03/08/2009, at 10:47 PM, Alexander Bokovikov wrote:

Can't agree. If we setup a control, as capable to have keyboard focus, then, activating this control, we activate all hierarchy of its parents, and we definitely can apply the "lowest level" parent's popup menu (if any) with its shortcuts. Of course, we can't do it, if we have no focusable controls, so we can work by mouse only in this case. But in this case we even can't speak about keyboard shortcuts. In any other cases we can.


There's much more to life than controls. Many views have elements that are spatially distributed and would not be considered controls but actual content. It is often useful to apply contextual menus to those elements, but almost impossible to meaningfully navigate them using just the keyboard. For example, in the Finder an icon view where the icons are not regularly ordered and spaced - keyboard navigation is hard. In fact the Finder makes a reasonable stab at this for selecting but you still can't activate the selected object(s) contextual menus without the mouse.

But back to your question - feel free to implement it if you feel it does make sense in your app. But I bet you'll find that the cost/ benefit of doing so is simply not worth it - users will be very unlikely to discover the feature (as it's not widespread in other apps) and understand how to manage the focus in an obvious way to make good use of it. The presence of a shortcut in a menu is so that the user, having clicked it so many times, notices that there's a quicker way to do whatever it is. The expectation then is that the shortcut will simply perform the action. If the user has to tab through umpteen views and somehow manipulate the selection just to get access to the shortcut, it's not really much of a shortcut, is it?

--Graham


_______________________________________________

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


  • Follow-Ups:
    • Re: [IB] - can't assign keyboard shortcut to a menu item
      • From: Alexander Bokovikov <email@hidden>
References: 
 >[IB] - can't assign keyboard shortcut to a menu item (From: Alexander Bokovikov <email@hidden>)
 >Re: [IB] - can't assign keyboard shortcut to a menu item (From: Graham Cox <email@hidden>)
 >Re: [IB] - can't assign keyboard shortcut to a menu item (From: Alexander Bokovikov <email@hidden>)
 >Re: [IB] - can't assign keyboard shortcut to a menu item (From: Graham Cox <email@hidden>)
 >Re: [IB] - can't assign keyboard shortcut to a menu item (From: Alexander Bokovikov <email@hidden>)

  • Prev by Date: NSPathControl - popup panel doesn't work
  • Next by Date: Adding more and more key/value observers is much too slow - workaround needed.
  • Previous by thread: Re: [IB] - can't assign keyboard shortcut to a menu item
  • Next by thread: Re: [IB] - can't assign keyboard shortcut to a menu item
  • Index(es):
    • Date
    • Thread