> In <znu-E93F54.10495515072003news.fu-berlin.de> ZnU wrote:
> > In article <20030713091723225-0700news.la.sbcglobal.net>,
> > matt neuburg <matttidbits.com> wrote:
> >> In <znu-27DE66.09010313072003news.fu-berlin.de> ZnU wrote:
> >> > I stuck:
> >> >
> >> > [[self window] makeFirstResponder:self];
> >> >
> >> > in acceptsFirstResponder. This seems to work.
> >> That seems really dangerous to me. Are you quite sure that you
> >> couldn't get the desired result by returning YES from both
> >> acceptFirstResponder and becomeFirstResponder, which is the
> >> canonical way to do it? m.
> > Positive. If I simply do that, becomeFirstResponder never even gets
> > called.
> But that's only because you're not doing anything to cause the NSMatrix
> subclass to be the first responder in the first place! It doesn't happen
> all by itself, you know.
> In other words, what I'm saying is, don't call makeFirstResponder inside
> acceptsFirstResponder - that's a sort of circular corruption of the
> framework - but do call it! In your window controller's awakeFromNib,
> for example, say something like this:
> [[myMatrix window] makeFirstResponder: myMatrix];