From kde-commits Wed Apr 30 23:13:22 2003 From: Chris Howells Date: Wed, 30 Apr 2003 23:13:22 +0000 To: kde-commits Subject: Re: kdebase/kdesktop/lock X-MARC-Message: https://marc.info/?l=kde-commits&m=105174443731951 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, On Thursday 01 May 2003 00:03, Antonio Larrosa Jiménez wrote: > Looks nice. Btw, how does this relate to the "DPMS-dependent" config option > in SaverEngine (lockeng.cc) ? That option prevents the screensaver from starting if an app like a media player has disabled DPMS so that the screen doesn't go blank half way through the film. This will SIGSTOP the screensaver when the screen has been blanked by DPMS -- if you've turned your monitor off, you probably don't want to have your CPU doing lots of processing as well :) > Could the timer (the checks) be completely disabled when the user doesn't > use DPMS ? (because he completely turned DPMS off in kcontrol) Yes, that would probably be a good idea. IIRC KDE takes over handling DPMS from X, but I'll have to check that tomorrow to be sure *yawn*. > Also, what happens if someone is using one of those screensavers that do > calculations while you're not using the computer? (like SETI, > protein-foldings, etc.) Would it be stopped when DPMS turn off the > monitor? (Not that I care about that, I suppose it's better to make those > real background processes instead of screensavers, but I thought I should > point it just in case). Hrm, interesting point. They would be a problem yes if they integrated with the KDE screensaver system, which I guess they don't. IIRC SETI just used to be a daemon that run in the background. - -- Cheers, Chris Howells -- chris@chrishowells.co.uk, howells@kde.org Web: http://chrishowells.co.uk, PGP ID: 33795A2C KDE: http://www.koffice.org, http://printing.kde.org, http://usability.kde.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE+sFiSF8Iu1zN5WiwRAkWhAJ0b4+MxV272I13+3TAf/GPsAXUWNACeLuo/ eU2OP2NbBHbmwoULB8siUt0= =bgvO -----END PGP SIGNATURE-----