Re: Disabling Exposé in SystemUIMode
Re: Disabling Exposé in SystemUIMode
- Subject: Re: Disabling Exposé in SystemUIMode
- From: Pierce Freeman <email@hidden>
- Date: Thu, 06 Aug 2009 15:24:28 -0700
- Thread-topic: Disabling Exposé in SystemUIMode
That's definitely a possibility. However, I am basically creating my
windows the same way that you are. The only difference is, I didn't set any
of those attributes and my main window just appears by "Cocoa default".
On 8/6/09 3:10 PM, "Ricky Sharp" <email@hidden> wrote:
>
> On Aug 6, 2009, at 10:10 AM, Pierce Freeman wrote:
>
>> Yeah, I completely copied his code and inserted it into my project.
>> Even
>> odder, it doesn't allow the Apple-Tab function (which is what it is
>> supposed
>> to do) but lets Exposé work just fine.
>>
>> I don't mean that it broke in the latest version of Leopard, as the
>> "old"
>> version I was using still did not have it enabled. I was wondering
>> if it
>> worked on Leopard at all, and based on your reply it does. So I
>> don't have
>> much idea as to what to try now.
>
>
> Hmm, I wonder if it has something to do with how I create my windows?
>
> I create "blanking" windows and put one of those on each screen
> (borderless window covers entire screen). Then, I create a content
> window (also borderless) that is then set to appropriate size (1024 x
> 768 in my case), centered on, and made a child of, the blanking window
> on the main screen.
>
> The call to SetSystemUIMode is made in applicationDidFinishLaunching:
> before I create windows.
>
> Both the blanking and content windows are subclasses of NSWindow.
>
> Blanking window's designated initializer is just a thin wrapper around
> NSWindow's initWithContentRect:styleMask:backing:defer:
>
> - styleMask is NSBorderlessWindowMask
> - backing is NSBackingStoreBuffered
> - defer is NO
>
> I then set these additional attributes:
>
> - hidesOnDeactivate (YES)
> - releasedWhenClosed (NO)
> - movableByWindowBackground (NO)
> - hasShadow (NO)
> - optimizedDrawing (YES)
> - opaque (YES)
>
> I also override canBecomeKeyWindow (returns NO) and
> canBecomeMainWindow (also returns NO).
>
>
> In my content window subclass, same setup as blanking window (in terms
> of attributes listed above). And, overrides to canBecomeKeyWindow and
> canBecomeMainWindow return YES.
>
>
> ___________________________________________________________
> Ricky A. Sharp mailto:email@hidden
> Instant Interactive(tm) http://www.instantinteractive.com
>
>
>
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please 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