Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!dimacs.rutgers.edu!rutgers!news.cs.indiana.edu!msi.umn.edu!cs.umn.edu!ariel.unm.edu!triton.unm.edu!stone
From: stone@triton.unm.edu (Andrew Stone)
Newsgroups: comp.sys.next
Subject: Re: Font Panel
Keywords: setBecomeKeyOnlyIfNeeded:
Message-ID: <1991Apr21.050414.3960@ariel.unm.edu>
Date: 21 Apr 91 05:04:14 GMT
References: <1991Apr20.185630.25903@engin.umich.edu> <1991Apr20.210513.4754@athena.mit.edu>
Followup-To: andrew@stone.com
Distribution: all
Organization: Stone Design
Lines: 21

In article <1991Apr20.210513.4754@athena.mit.edu> efc@athena.mit.edu (E.Celeste) writes:
>> Has anyone noticed under 2.0 that the Font Panel (among others) *never*
>> ever becomes the key window?
>
>The Font Panel *does* become the key window if you click in the font size
>text field to type in a non-standard point size.
>
>...Eric
>
>--
>E.Celeste

Actually, the font panel has its setBecomeKeyOnlyIfNeeded: set to YES, which
prevents unnecessary calls to windowDidBecomeKey: on your document. I did
this in Create to the main inspector, which can be annoying when you want to
type in a value: you kind of have to type hard and sometimes twice. 

On the other hand, if you are just clicking interface buttons, needless
state changes are avoided.

andrew