[MPlayer-dev-eng] Fwd: Re: accessibility misfeatures

[Michael Niedermayer]

Hi

On Tuesday 11 January 2005 11:28, Amaury Jacquot wrote:
> Jindrich Makovicka wrote:
> > Alexander Strasser wrote:
> >> I think you are right!
> >> This code sends an event of type SCREENSAVER with the content
> >> DEACTIVATE. This should be equal to fire up a xscreensaver-command
> >> -deactivate. And this pretends a user interaction meaning
> >> - if the screen was blanked => unblank it
> >> - if the screen wasn't blanked => reset the timeout.
> >>
> >> So either these accusations are wrong or there is more xscreensaver code
> >> in mplayer we don't know of. But i really don't think so.
> >
> > Actually, there is (or was, i didn't check if it's fixed) a different
> > XScreensaver vs. MPlayer issue. XScreensaver periodically re-enables
> > DPMS, regardless of screensaver pings, which means the screen turns off
> > in the middle of a movie anyway.
>
> mebbe we need a standard way to communicate to Xscreensaver that
> screensaver should be off ?

there is a standard way, killall -s KILL xscreensaver

[...]
-- 
Michael

"In any case, just because code is syntactically "valid" GNU C doesn't 
mean gcc can always compile it." -- justification to close a gcc bug