[MPlayer-dev-eng] [RFC] kde screensaver stuff using system()
zuxy.meng at gmail.com
Wed Feb 7 10:51:04 CET 2007
2007/2/7, Reimar Doeffinger <Reimar.Doeffinger at stud.uni-karlsruhe.de>:
> On Wed, Feb 07, 2007 at 02:16:36PM +0800, Zuxy Meng wrote:
> > 2007/2/7, Diego Biurrun <diego at biurrun.de>:
> > >On Mon, Feb 05, 2007 at 03:53:10PM +0100, Reimar Döffinger wrote:
> > >> I do feel a bit uncomfortable about this, it seems extremely like a hack
> > >> to me.
> > >> Is there no better way?
> > >> Do we really have to handle this screensaver mess?
> > >> Any other comments?
> > >
> > >We were talking about this on IRC the other day. A problem that we
> > >currently have is that gnome screensaver is not stopped, which is an
> > >annoyance for users. An annoyance that distros have started working
> > >around in multiple different and mostly hackish ways.
> > >
> > >A way out of this dilemma might be generating keypress events at regular
> > >intervals. It promises to work across all platforms and not need to be
> > >extended for the screensaver du jour ..
> > Ever since Win98 Windows provides an API called
> > SetThreadExecutionState() that can be used as a heartbeat function to
> > prohibit screensavers. Anything similar in X Windows?
> It saddens me to say, but even without that in this regard windows is
> ahead: it sends the active window a message that asks for permission to
> activate the screensaver, and AFAIK this is even already used in MPlayer...
Although it ceases to work when the user selects to protect the
screensaver with a password:-)
> I think it was really a bad idea that applications have implemented such
> hacks as our kde screensaver support, it works like crap but good enough
> to take away the pressure to find a real solution.
Beauty is truth,
While truth is beauty.
PGP KeyID: E8555ED6
More information about the MPlayer-dev-eng