FROM : Justin Anderson
DATE : Sat Jul 15 14:57:36 2006
But would the menu then still flash as though a menu item had caught
the key equivalent?
Would it be better in your NSWindow or NSApp subclass to eat the Cmd-
= event and create a new Cmd-+ event from scratch?
Justin Anderson
On Jul 14, 2006, at 4:54 PM, I. Savant wrote:
>
> This is not what the OP is asking. The question was, to
> paraphrase, how to trigger the "make it bigger" command with Cmd-=
> instead of Cmd-shift-= when you've set the key equiv to Cmd-+ ...
>
> I'm thinking the window itself could trap and respond to Cmd-=
> and let the menu handle Cmd-+ normally. It may not be pretty but
> that's how I achieve the same thing (subclassing NSWindow and
> responding to the key combo, forwarding all others to super).
>
> --
> I.S.
DATE : Sat Jul 15 14:57:36 2006
But would the menu then still flash as though a menu item had caught
the key equivalent?
Would it be better in your NSWindow or NSApp subclass to eat the Cmd-
= event and create a new Cmd-+ event from scratch?
Justin Anderson
On Jul 14, 2006, at 4:54 PM, I. Savant wrote:
>
> This is not what the OP is asking. The question was, to
> paraphrase, how to trigger the "make it bigger" command with Cmd-=
> instead of Cmd-shift-= when you've set the key equiv to Cmd-+ ...
>
> I'm thinking the window itself could trap and respond to Cmd-=
> and let the menu handle Cmd-+ normally. It may not be pretty but
> that's how I achieve the same thing (subclassing NSWindow and
> responding to the key combo, forwarding all others to super).
>
> --
> I.S.
| Related mails | Author | Date |
|---|---|---|
| Shoaib Hannani | Jul 14, 21:59 | |
| Michael Watson | Jul 14, 22:44 | |
| I. Savant | Jul 14, 22:54 | |
| Justin Anderson | Jul 15, 14:57 | |
| Bill Monk | Jul 15, 20:20 |






Cocoa mail archive

