FROM : David Dunham
DATE : Fri Oct 15 18:46:13 2004
Scott:
>> menu items which have things like the return key or ^C as keyboard
>> equivalents
>
> Not sure what you mean by "return key", but the ^ character refers to
> the Control key.
The key labeled "return." It shows up as an obscure glyph in the menu.
(IIRC, it's a pain to enter it in IB.)
> Ironically, using Control as a key equivalent turns your fingers into
> a pretzel. Stick to command, shift and option as much as possible.
Ironically, I asked for technical, not UI, advice. In further irony,
the actual control key is for a debug menu item, which I won't be
exposing users to.
j o a r:
> Keyboard shortcuts *without* the NSCommandKeyMask was previously not
> propagated through the first responder chain, and to menu items, like
> keyboard shortcuts *with* the NSCommandKeyMask.
> I filed bug reports with Apple about this, and they claim to have
> solved at least some of it (I think back in 10.2.6). I have not
> verified that they have however, as my workaround was already in
> place, and is working fine (overriding NSApplication sendEvent and
> manually checking the responder chain and menu items).
This is likely what I'm seeing -- I'm pretty sure my control equivalent
is handled high enough up the responder chain that it's not a problem
with focus.
Is your code pretty simple then?
David Dunham A Sharp <email_removed>
Voice/Fax: 206 783 7404 http://a-sharp.com
Efficiency is intelligent laziness.
DATE : Fri Oct 15 18:46:13 2004
Scott:
>> menu items which have things like the return key or ^C as keyboard
>> equivalents
>
> Not sure what you mean by "return key", but the ^ character refers to
> the Control key.
The key labeled "return." It shows up as an obscure glyph in the menu.
(IIRC, it's a pain to enter it in IB.)
> Ironically, using Control as a key equivalent turns your fingers into
> a pretzel. Stick to command, shift and option as much as possible.
Ironically, I asked for technical, not UI, advice. In further irony,
the actual control key is for a debug menu item, which I won't be
exposing users to.
j o a r:
> Keyboard shortcuts *without* the NSCommandKeyMask was previously not
> propagated through the first responder chain, and to menu items, like
> keyboard shortcuts *with* the NSCommandKeyMask.
> I filed bug reports with Apple about this, and they claim to have
> solved at least some of it (I think back in 10.2.6). I have not
> verified that they have however, as my workaround was already in
> place, and is working fine (overriding NSApplication sendEvent and
> manually checking the responder chain and menu items).
This is likely what I'm seeing -- I'm pretty sure my control equivalent
is handled high enough up the responder chain that it's not a problem
with focus.
Is your code pretty simple then?
David Dunham A Sharp <email_removed>
Voice/Fax: 206 783 7404 http://a-sharp.com
Efficiency is intelligent laziness.
| Related mails | Author | Date |
|---|---|---|
| David Dunham | Oct 15, 07:37 | |
| Scott Stevenson | Oct 15, 09:55 | |
| Alex v.Below | Oct 15, 10:47 | |
| j o a r | Oct 15, 10:58 | |
| David Dunham | Oct 15, 18:46 | |
| j o a r | Oct 15, 21:47 | |
| Scott Stevenson | Oct 15, 23:52 | |
| David Dunham | Nov 27, 05:28 |






Cocoa mail archive

