[Dalgo]

I looked as Apple's ColorBars example and I figured out how to take over a few displays and draw directly to them. This is pretty cool since I can do full screen previews of stuff and be guaranteed not to have any windows above it. Anyway, I was wondering how I might go about getting user input while I have taken over the screen. Since events are handled by windows, and this isn't a window, how can I handle events while it is in full screen mode? This is a big necessity since if you want a slide show or something you're going to need some way of moving to the next slide or quitting.

[Ryan Bates]

Where is the Color Bar example? I can't find it on Apple's sample code area - assuming it's cocoa.

Anyhow, I created a full screen view using a window the same size as the screen, giving it an NSBorderlessWindowMask, then putting the level at NSScreenSaverWindowLevel (this puts the window above everything, menu and dock, just like a screen saver) Are there any disadvantages in creating a full screen window instead of drawing directly to a screen display? Is it slower? I had a few problems getting keyboard events this way using the Public Beta, but it seems to be fixed in the final.

Sorry if this wasn't what you were looking for.

Ryan

[geran]

Hi, anyone knows if finder still draws the desktop icons on the same layer as the desktop picture, It would be cool whit a app that runs screensavers on the desktop, (a ported freespace for macos x server to public beta and it over drawed the desktop icons). But it looked cool...

[Dalgo]

You can find the colorbar example at http://developer.apple.com/samplecod.../ColorBars.htm
The description seems to be the same as that for Mode Whacker which you can get at http://developer.apple.com/samplecod...odeWhacker.htm They are two different things, however. The colorbar example locks the focus on a screen and then draws directly to the screen. It's written in C, not objective C although there is no reason why you can't call the core graphics functions in an Objective C method.

[ryochiji]

Why not use BeginFullScreen() and EndFullScreen()? It doesn't let you "commandeer" the display (you can switch to other apps with command-tab) but I would imagine it to be sufficient for most purposes. BeginFullScreen creates a window for you that covers the entire display, so the standard event handling scheme works fine too.

There's a nice and simple sample code at: http://developer.apple.com/samplecod...FullScreen.htm

[Dalgo]

Hmmm... I'm not sure if it'll play well with Objective C since the project includes the libstdc++.a and Carbon/Carbon.h but those might not be essential for it's use so I guess that I could try doing it that way without that library and see if it works. The Quicktime headers look like they are all C, not C++ but I didn't look thoroughly.

[Angus_D]

You can call Carbon code from a Cocoa app, take a look at Apple's example in the Cocoa section of their sample code site... It's not particularly pretty, but it works