Re: the mechanics of writing over fullscreen
Re: the mechanics of writing over fullscreen
- Subject: Re: the mechanics of writing over fullscreen
- From: Ricky Sharp <email@hidden>
- Date: Mon, 10 Sep 2007 11:11:07 -0700
On Monday, September 10, 2007, at 10:54AM, "Jaime Magiera" <email@hidden> wrote:
>I'm trying to write a floating window over a full sreen display
>(keynote presentation). After searching the archives, the best
>solution seems to be CGShieldingWindowLevel(). So, I call the
>following after the presentation goes into fullscreen...
>
>[aSmallWindow setLevel:CGShieldingWindowLevel()];
>
>when I'm done with the floating window, I call...
>
>[aSmallWindow orderOut:self];
>
>On some machines, this works fine. On other machines, the window
>image stays on the screen until the person moves to the next slide
>(i.e. does a redraw).
>
>Is there something I should call to force a redraw? I can't figure
>out why there would be different behavior on different machines. Is
>there a better way to draw above a fullscreen mode? Perhaps there is
>something with the floating window being faster/slower than the main
>window going into fullscreen? hmmmm.
Short answer: you cannot mix AppKit with a captured screen. (I'm assuming your floating window is some instance of NSWindow and the full-screen presentation your talking about has already captured the screen with the CG API calls)
If the display has already been captured, you'll need to do drawing yourself onto it.
--
Rick Sharp
Instant Interactive(tm)
_______________________________________________
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