On Apr 23, 2008, at 12:37 AM, Ken Thomases wrote:
See this:
http://developer.apple.com/documentation/Cocoa/Conceptual/EventOverview/EventArchitecture/chapter_2_section_6.html
and also -[NSResponder setNextResponder:].
However, NSWindowController automatically uses that method to add
itself as the next responder after the window it manages. That's
illustrated in the above link. So, I don't think you need to do
anything special.
I did all that; that's not really what I want.
My NSWindowController subclass is not automatically hooked up (I
tried). I am able to use the setNextResponder et al. to put it *after*
the app, but I can't figure out how to set it up so it'll be *before*
the app.
What I have works, but kinda bugs me, because the app is "more final"
than my controller.
--
Rick
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
