Smarter Screen saver

[Alvin Thompson]

On Thu, 2005-09-22 at 10:24 +0100, Thomas Beckett wrote:
> The idea for the postpone time was that if the player did crash before
> the film or whatever you are doing finishes then the resume signal
> would not need to be issued, it would wake itself up.

i'm not a big fan of the "postpone time" concept. for one, it's quite
possible that totem/whatever has no way of knowing the play time (like
with a live stream). then, it would have to resort to sending a postpone
every few minutes, which would be inelegant. also, why stop the screen
saver for 2 hours when you had to kill the program at 2 minutes?

instead of a postpone time, how about including the PID of the app
sending the POSTPONE message? then, if that process ends without
canceling the POSTPONE, the screen saver program knows to do so itself
(for now, see below)?

i don't know anything about how DBUS works now, but can it be patched to
be made aware of the concept of "cancelable" messages? the job of noting
the PID of a program which sends a cancelable message (like this
SCREENSAVER_POSTPONE) and issuing a CANCEL_SCREENSAVER_POSTPONE message
if the process ends without canceling it itself really belongs there.

my 2 cents,
alvin

-- 
Alvin Thompson

Navy: 42
Army: 13