Re: gnome-screensaver 0.0.23
- From: Richard Hughes <hughsient gmail com>
- To: Rodrigo Moya <rodrigo novell com>
- Cc: screensaver-list gnome org
- Subject: Re: gnome-screensaver 0.0.23
- Date: Thu, 05 Jan 2006 18:02:45 +0000
On Thu, 2006-01-05 at 11:40 +0100, Rodrigo Moya wrote:
> On Wed, 2006-01-04 at 16:47 -0500, William Jon McCann wrote:
> > Hi,
> >
> > Jaap Haitsma wrote:
> > >>hmm, IIRC, the typing break in gnome-settings-daemon does idle
> > >>detection, so maybe we should be using that instead of having it on the
> > >>screensaver? The problem is the typing break does not have any DBUS
> > >>interface, so it would need to be added.
> > >
> > > I like the idea of having this in gnome settings daemon. IIRC g-s-d only
> > > looks at the keyboard and not at the mouse. So mouse idleness should be
> > > added as well
> >
> > What is the advantage of having it in gnome-settings-daemon?
> >
> > At the moment gnome-settings-daemon doesn't have idle detection. It has
> > a very crude type of activity detection.
> >
> > In order to decouple idle detection from the screensaver you will need
> > to solve a number of tricky technical problems. How do you handle
> > "inhibitors"? How do you handle races between idle and screensaver
> > activation states? What is the sequence of events when the lock screen
> > button is pressed? How do you do idle activation warnings? And so on.
> >
> > Seems more reasonable to make the typing break program gnome-screensaver
> > aware.
> >
> yes, indeed sounds more reasonable.
I think this makes most sense. The idle detection stuff in g-s-d is not
easy to fix, perhaps best to change users to the new g-s API and rip the
broken stuff out of g-s-d.
Richard.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]