Re: setKeyEquivalent: gives two action invocations
Re: setKeyEquivalent: gives two action invocations
- Subject: Re: setKeyEquivalent: gives two action invocations
- From: Roland Torres <email@hidden>
- Date: Mon, 26 Mar 2007 17:36:56 -0700
Yes, subclassing NSButton and overriding -performKeyEquivalent works
great, and it handles the case for all buttons with one change, as
opposed to inserting a check for NSKeyUp in each button's action
routine.
Thanks,
Roland
On Mar 24, 2007, at 3:14 AM, Wain Glaister wrote:
Hi,
Take a look at <http://www.cocoadev.com/index.pl?
NSButtonFunctionKeyEquivalent>
It uses the same technique as suggested by Ken but at a higher
level and so will prevent the flicker.
Wain
On 23 Mar 2007, at 17:24, Roland Torres wrote:
Hi Ken,
This works well. The only slight side effect to this is that the
button on the GUI flickers twice (once per key-down, once per key-
up), but I can live with it!
Thanks!
Roland
On Mar 22, 2007, at 9:41 PM, Ken Ferry wrote:
Hi Roland,
This is a bug. Key equivalents with the function key mask set and
without the command key modifier are sent for both key up and key
down.
You can work around it in a future proof way with code like this:
- (IBAction)myAction:(id)sender {
if ([[NSApp currentEvent] type] == NSKeyUp)
return;
...
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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