Re: doubleAction problems
Re: doubleAction problems
- Subject: Re: doubleAction problems
- From: Sherm Pendley <email@hidden>
- Date: Sat, 11 Dec 2004 22:25:28 -0500
On Dec 11, 2004, at 9:39 PM, Danny Swarzman wrote:
That didn't help. I'm surprised the compiler doesn't care which syntax
I use.
There's no reason why it would care, at that point - and not much it
could do about it if it did.
A @selector is just a selector, with no attachment to a particular
class. And when you pass it to setDoubleAction:, no checking is done to
ensure that the target actually implements the corresponding method.
There's no foolproof way to ensure that, really. You might not have set
the target yet - all that's necessary is that you set it before the
action is fired. Even if the target doesn't have the method when you
call setDoubleAction: you could use runtime functions and/or load a
bundle to add it later. You could use forwardInvocation: to handle the
action message some other way. And so forth.
Anyway, the method name was the first thing that leaped out at me -
I'll have a look at the rest.
sherm--
Cocoa programming in Perl: http://camelbones.sourceforge.net
Hire me! My resume: http://www.dot-app.org
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden