efc@athena.mit.edu (E.Celeste) (04/21/91)
> 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
stone@triton.unm.edu (Andrew Stone) (04/21/91)
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
dejnsen@caen.engin.umich.edu (Nik Anthony Gervae) (04/22/91)
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 But shouldn't it become the key window when you just click in or on it anyway? I see a return symbol on a button in a window I just clicked, I'm inclined to hit return. Gripe grumble mumble..... ;-) -- / Nik Gervae aka dejnsen@caen.engin.umich.edu | "It'll be finished next week, \ | CS/Linguistics stud. & NeRD at UM (go blow) | I promise!"--me | | | | | **When all else fails, bug someone who | "Just say an iguana chewed | \ knows (not me!). | up your textbook."--Jason Fox /