Re: screensaver events

Thu Jan 16 2003, Neil Stevens wrote:
> > If an app does "pause" and then crashes there won't be a resume,
> > so a "reset" option which resets the timer would be better(or also
> > needed). Or did I miss something?
> 
> Hm, good point.  I suppose an app that uses pause should have a crash 
> handler that will resume.
> 
> Reset would require the app to do so at intervals, which would be 
> inefficient.
> 
How inefficient would it be with dcop? 
We use the "reset" model at intervals for both xscreensaver and for the 
x internal one (XResetScreenSaver).
Even with a signal handler you won't be able to catch kill/stop.
I think both methods should be available. 

The best would be if there was some standard way to do this for all
screensavers. Something like:
The screensaver sets a property on the
root window which contains a window id that the screensaver listens for.
(Like the windowmanagers do)
Using SendEvent one can send the on/off/reset commands to the
screensaver without knowing anything more.
This would be efficient and you wouldn't need to start different
external programs for different screensavers.

/Björn