Re: Showing numpad key equivs in menu items
Re: Showing numpad key equivs in menu items
- Subject: Re: Showing numpad key equivs in menu items
- From: Steve Mills <email@hidden>
- Date: Tue, 07 May 2013 08:29:19 -0500
On May 7, 2013, at 02:04:09, Kyle Sluder <email@hidden> wrote:
> This is a terrible argument, and you know it not to be true. If you showed those three glyphs to a non-Western person, would they be likely to discern a difference? Depending on the arguments I pass, even my _computer_ won’t distinguish between them.
Then you have a pretty dumb computer.
> That's because at some point you learned their meaning. There's nothing intuitive about putting a number in a round rect to indicate anything is different about that number, much less _what_ specifically is different. For the record, I believe I’ve only encountered this convention in Adobe apps.
And at some point you learned that a crooked angled line with a dash at the top-right meant "option key", even though there have been very few (if any) keyboards manufactured with that symbol printed on the option key. Same with ^ and the control key. That doesn't mean it's wrong to use those symbols.
> If this were a more practiced convention on OS X, then I'd be quite more disposed towards your argument. But so-called “real” Macs have been shipping without numpads for quite some time, and developers in general have no reason to assume users are familiar with numpad-variant shortcut indicators.
And most "real" users buy extended keyboards. I've never seen someone who works with spreadsheets NOT have a keyboard with a numpad, or people in the film or music industries who need all the keys they can get.
> I agree with you wholeheartedly that this right here is a bug. If Apple decides to fix it (not likely, I’d guess) then they might pick a more meaningful convention than enclosing the numerals in round rects.
If they do, that's just great, but for the past however many years, many users are familiar with the current scheme.
> Moreover, we don't know your constraints. We don't share your motivations. We are not mechanical Turks and do not live to answer within parameters.
Exactly, you don't know our constraints or our users. This is a technical list, and I expect technical answers, not opinions that waste everyone's time.
--
Steve Mills
office: 952-818-3871
home: 952-401-6255
cell: 612-803-6157
_______________________________________________
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