On Feb 19, 2005, at 9:46 AM, Matt Neuburg wrote:
On Fri, 18 Feb 2005 23:18:00 -0500, "Andrew O'Laughlin"
<email@hidden>
said:
Apple's event handling says that a windows delegate is part of the
responder chain, and that the delegate doesn't need to inherit from
NSResponder.
If it says that, then "Apple's event handling" lies.
I'm making a simple application, and subclassing NSWindow seems
like
overkill for interpreting a few keyDown and keyUp events. How would
my
window's delegate respond to those events? Implementing
keyDown:(NSEvent *)event in the delegate doesn't do the trick
though
the documentation seems to imply that it would.
It wouldn't. A window's delegate is not part of the chain.
Actually, it is, but it's after the window itself. In this case, the
event is probably getting consumed by the window. IIRC, NSWindow's
-keyDown: method just plays a beep sound.
According to the docs:
the full responder chain comprises these objects:
The key window’s first responder and successors, including objects
added with setNextResponder:
The key window itself
The key window’s delegate (which need not inherit from NSResponder)
The main window’s first responder and successors, including objects
added with setNextResponder:
The main window itself
The main window’s delegate (which need not inherit from NSResponder)
The application object, NSApp
The application object’s delegate (which need not inherit from
NSResponder)