screensaver madness...
screensaver madness...
- Subject: screensaver madness...
- From: "Matt Pease" <email@hidden>
- Date: Wed, 23 Apr 2003 13:28:30 +0200
Hello all-
I've got a couple questions regarding the cocoa ScreenSaverView api.
1. Is it possible for the saver to quit itself? Can I send a message
somehow to the parent class that its time to stop? or,
2. Can I get a CGraphPtr to the ScreenSaverView window? I could
send this along to my Carbon saver to give it what it needs to draw.
What got me into this mess...
For certain reasons, my screensaver needs to be written in Carbon / CFM.
So I'm using a "shell" cocoa saver extending the ScreenSaverView class.
My "saver" simply sends an apple event to my carbon app from it's
startAnimation method.
My carbon app (the real saver), creates a full-screen window, raises itself
topmost
(using SetFrontProcess & UDesktop::SelectDeskWindow -- a powerplant class)
& begins drawing.
What happens is this: the "shell" saver (Cocoa) window takes over the
screen, and
somehow my app can't draw. However, if I move my mouse a little, the cocoa
"saver" quits & then the carbon app is able to draw.
I tried returning "NO" from performGammaFade; over-riding drawRect
with an empty fxn; & setting backingStoreType to NSBackingStoreNonretained.
I get the feeling that ththe Cocoa ScreenSaverView system severely limits
what can be done from the screensaver-- probably for security reasons?
Anyhow, it'd be sweet to hear what anyone here thinks of this.
Thanks-
Matt
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.