Screen saver receiving repeated initwithframe calls
Screen saver receiving repeated initwithframe calls
- Subject: Screen saver receiving repeated initwithframe calls
- From: Norman Palardy <email@hidden>
- Date: Tue, 29 May 2007 23:18:51 -0600
I've implemented a screen saver using the screen saver template
provided by XCode. This ends up being just a screen saver shell that
starts a different application that is the actual screen saver. I
have no choice but to do it this way since the screen saver is not
implemented in Xcode.
The application that gets started runs fine for the most part but the
XCode screen saver shell is getting numerous initwithframe calls one
after the other whether I have one or more monitors.
I've hunted and found a few bits of information on this happening
with multiple monitors but I'm seeing the screen saver engine call my
screen saver shell repeatedly like this with a single monitor attached.
What I'm not clear on is when the screen saver engine actually
instantiates my class and calls initwithframe does my class stay
resident until the screen saver is dismissed ? (I expect it does but
want to be sure)
If the answer to this is that the instance of my class does stay
resident why would I get repeated initwithframecalls ?
This is about the last big glitch I have with this set up that I need
to solve.
Thanks for any advice or help you can offer.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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