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 18:59:04 -0500
On Sep 10, 2007, at 5:16 PM, Thomas Engelmeier wrote:
On 10.09.2007, at 20:11, Ricky Sharp wrote:
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.
Would you mind to elaborate a little bit? I have a shipping (single
window) kiosk app that captures the main screen and does some
Frontrow-esque stuff in the main NSWindow (with a dynamically
changing set of NSViews subclasses)... It's in a "controlled
environment", but none of the four test machine-types had any
problems besides the coordinate system that does not get reset
instantly after changing the resolution....
Definitely search the archives on both cocoa-dev (and especially
quartz-dev). I've quoted threads originating from an Apple engineer
stating to avoid this. It's something that will not work on all
hardware configs.
My kiosk-type apps (which use AppKit) just uses simple NSWindow
subclasses to provide a full-screen experience. I've posted other
threads on this to cocoa-dev in the past (e.g. how to use child
window APIs to give you good blanking windows)
___________________________________________________________
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