Re: is the nextKeyView really used by Cocoa ?
Re: is the nextKeyView really used by Cocoa ?
- Subject: Re: is the nextKeyView really used by Cocoa ?
- From: Stéphane Sudre <email@hidden>
- Date: Wed, 11 Jul 2001 14:39:18 +0200
On mercredi, juillet 11, 2001, at 02:09 PM, Jean-Frangois Veillette
wrote:
>
the window's initialFirstResponder had to be set, and part of the chain.
>
Try to set it to your NSTextField1.
With the initialFirstResponder set, it's now working.
But I have no recollection of needed to set the initialFirstResponder to
make it work with some code on Mac OS X Server.
And I don't see the relation between the initialFirstResponder and the
nextKeyView mechanism.
The doc says:
setInitialFirstResponder:
<Attachment missing>
Sets aView as the NSView that's made first responder (also called the
key view) the first time the receiver is placed on screen.
If I make a tab in a NSTextField, I tend to believe the next key view is
the one you can get with the - (NSView) nextKeyView; method.
How does initialFirstResponder get involved here ?
The Key view loop is built by IB with the nextKeyView connection which
also gives the previousKeyView info. So why does it need to know the
initialFirstResponder ?
The initialFirstResponder is only useful for these cases: first time the
window is shown, tab when a view has no nextKeyView, isn't it ?