Re: initialFirstResponder weirdness
Re: initialFirstResponder weirdness
- Subject: Re: initialFirstResponder weirdness
- From: Allan Odgaard <email@hidden>
- Date: Sat, 6 Jul 2002 09:52:51 +0200
On fredag, juli 5, 2002, at 05:38 , email@hidden wrote:
[...]
It never seems to 'become' the first responder, nor does my class
accept keyboard inputs (it just beeps). Looking at the Cocoa
documentation for NSWindow, I can't see anything that prevents window
responders from being 'just' NSResponders, and not NSViews.
Does anyone have any information about what's going on, and where this
is documented?!?
I really think initialFirstResponder is broken -- at least for me: if I
log firstResponder and initialFirstResponder in awakeFromNib, then these
to variables differ.
So instead set it programmatically, and use makeFirstResponder rather
than setInitialResponder -- however, firstResponder needs to be an
"NSView *" -- but you can setNextResponder to an "NSResponder *" (which
is perfectly legal, and works fine :-) ).
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.