Re: Preventing application from becoming active (SOLVED)
Re: Preventing application from becoming active (SOLVED)
- Subject: Re: Preventing application from becoming active (SOLVED)
- From: Felix Schwarz <email@hidden>
- Date: Fri, 2 Mar 2007 02:13:54 +0100
I've found the solution by overriding -
shouldDelayWindowOrderingForEvent.
Best regards,
Felix
On 02.03.2007, at 01:55, Felix Schwarz wrote:
I've overridden
- (BOOL)canBecomeKeyWindow
- (BOOL)canBecomeMainWindow
- (BOOL)acceptsFirstResponder
so far, all returning NO. That prevents the window from becoming
active, but my application still becomes active.
To also add a bit more info on why I need this behaviour:
My application becoming active is a problem as a press in my custom
view will - among other things - emulate keyboard events that have
to go to the currently active app (i.e. to enter text), not my app.
Best regards,
Felix
On 02.03.2007, at 01:27, Kam Dahlin wrote:
Can you override NSWindows - (BOOL)canBecomeMainWindow method and
return NO?
Kam Dahlin
Studio Systems Specialist
Vulcan Studio Group
Vulcan Inc.
email@hidden
The best time to add insult to injury is when you are signing
someones cast.
On Mar 1, 2007, at 4:23 PM, Felix Schwarz wrote:
Hi there!
I've a borderless NSWindow containing a custom NSView that provides
tools to other applications. Now to the problem:
A click in my borderless window's custom NSView should get
handled by
the NSView via standard -mouseUp:/-mouseDown: selectors but
*without*
my application and its windows becoming active at all.
How can I achieve this?
Thanks in advance for any help!
Best regards,
Felix
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden