Re: NSWindow/NSPanel UI-violating question
Re: NSWindow/NSPanel UI-violating question
- Subject: Re: NSWindow/NSPanel UI-violating question
- From: Shaun Wexler <email@hidden>
- Date: Thu, 3 Jul 2003 22:52:54 -0700
On Monday, June 30, 2003, at 10:15 AM, Sailor Quasar wrote:
I have an NSWindow and a utility NSPanel in my application (both
awakened from the main nib at launch time), along with a companion nib
which creates an NSWindow (not the document architecture though)
several times throughout execution. What I need is for the utility
NSPanel to take the Carbon behavior of palette windows and be always
activated and always receiving keystrokes. I've tried overriding the
NSWindows so that canBecomeKeyWindow: returns NO, but that while that
gives the utility window the correct status, it makes all the other
windows permanantly look deactivated. I need the top NSWindow among
them to Look active even though it's not receiving keystrokes. I've
played around with canBecomeKeyWindow: and canBecomeMainWindow: alot,
and I'm beginning to think I'm going to have to sabotage the elegance
of Cocoa's event handling by dealing with activation and key events
myself, at a level that would approach the old pre-Carbon WNE days.
Someone please tell me a better solution!
- (BOOL) isKeyWindow
{
return YES;
}
--
Shaun Wexler
MacFOH
http://www.macfoh.com
_______________________________________________
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.