[MPlayer-dev-eng] [PATCH] Use XScreenSaverSuspend if supported

[Ivan Kalvachev]

On Dec 21, 2007 9:11 PM, Rich Felker <dalias at aerifal.cx> wrote:
> On Fri, Dec 21, 2007 at 10:00:39AM +0100, Reimar Döffinger wrote:
> > Hello,
> > On Fri, Dec 21, 2007 at 08:00:49AM +0100, Adam Tlałka wrote:
> > [...]
> > > So while using XScreenSaverSuspend according to a) screensaver could be
> > > forcibly activated by other app and as stated in b) XScreenSaverSuspend
> > > call will not deactivate already active screen saving mode - so if you
> > > start mplayer from some script there will be no screen saver
> > > deactivation.
> >
> > XScreenSaverSuspend actually seems like the much more sensible behaviour
> > to me, why should we e.g. disallow explicit locking of the screen via the
> > screensaver application just because MPlayer is running?
>
> I agree, this is the correct behavior. If someone wants to do odd
> scripting things, just run a separate command to unblank the screen
> before starting MPlayer. But MPlayer should not go to lots of trouble
> to inhibit the correct, sane default behavior.

Seconded.
BTW, the XReset* would work only on the screensaver, not dpms.

Reimar, I'm against KDE removal and exactly because there are KDE
versions that doesn't honor XSS. However I think that it should only
be triggered by command line (aka
-stop-screensaver=kde/gnome/xscreensaver ). I won't mind if all this
crap is removed if we commit the event generator (mouse movement
etc...).

One more remark, xscreensaver seems to honor XSS extension if
available (it even have workarounds for quite many history bugs in
it).