FROM : Andrew Merenbach
DATE : Sat Jun 21 20:47:25 2008
On Jun 21, 2008, at 11:00 AM, Georg Seifert wrote:
>>> I use the panel as a palette. Something like the systems font
>>> chooser.
>>> They have the close button enabled, but do not responde to close
>>> commands from the keyboard.
>>
>> Using TextEdit as an example, the font panel *will* close on
>> command-w, if
>> it becomes key. It is just that it won't become key unless/until all
>> document windows are closed. This is the expected behavior I was
>> talking
>> about.
>
> I cannot reproduce this. If I close all documents in Textedit (or
> any other Mac-App) the font panel stays there and I get a NSBeep on
> hitting command-w.
Hi! If you click on the Font panel's title bar before you hit command-
w, you will see it activate -- then, when you do hit command-w, it
*will* close. Thus it does indeed respond to the keyboard shortcut.
Perhaps you can work some magic with -(BOOL)canBecomeKeyWindow or -
(BOOLcanBecomeMainWindow?
Cheers,
Andrew
DATE : Sat Jun 21 20:47:25 2008
On Jun 21, 2008, at 11:00 AM, Georg Seifert wrote:
>>> I use the panel as a palette. Something like the systems font
>>> chooser.
>>> They have the close button enabled, but do not responde to close
>>> commands from the keyboard.
>>
>> Using TextEdit as an example, the font panel *will* close on
>> command-w, if
>> it becomes key. It is just that it won't become key unless/until all
>> document windows are closed. This is the expected behavior I was
>> talking
>> about.
>
> I cannot reproduce this. If I close all documents in Textedit (or
> any other Mac-App) the font panel stays there and I get a NSBeep on
> hitting command-w.
Hi! If you click on the Font panel's title bar before you hit command-
w, you will see it activate -- then, when you do hit command-w, it
*will* close. Thus it does indeed respond to the keyboard shortcut.
Perhaps you can work some magic with -(BOOL)canBecomeKeyWindow or -
(BOOLcanBecomeMainWindow?
Cheers,
Andrew






Cocoa mail archive

