Screensaver question
Screensaver question
- Subject: Screensaver question
- From: David Gish <email@hidden>
- Date: Mon, 5 Mar 2007 17:56:21 -0600
Does anyone know of a way to capture keyboard and mouse events in an
OS X screensaver app in order to provide a degree of interactivity
and allow the screensaver code itself determine when to exit? I'm a
relative newbie to Cocoa, but it looks like this would require
modifying or replacing the default NSRunLoop instance
(currentRunLoop) so events can be redirected. Screen savers are
written essentially as plugins and stealing the run loop from the
host app (ScreenSaverEngine) seems very unkosher to me. And there's a
complicating factor. Sniffing around in gdb, it appears that a system
with one display runs ScreenSaverEngine and the screen saver itself
in a single thread, but with additional displays, a thread is spawned
for each screen saver.
My idea at this point is to simply write a screensaver stub that
launches a real full-screen app. The control panel preview would have
to be handled separately. Any other ideas?
Thanks,
_______________________________________________
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