Re: Fwd: [Usability] Technical language in applet menus

[Kirk Bridger <kbridger shaw ca>]

I'm still not clear on when a user should ever have to "restart a
screensaver".  That makes no real sense for a desktop.

You either have the screensaver enabled, or you don't.  So perhaps
having the daemon automatically started when the user selects a
screensaver, and then stopped when they choose no screensaver.

What use-case does this control idea not capture and deal with?  In the
case of compiling, just choose no screensaver and it will kill the
daemon for you.

Kirk


On Sat, 2005-05-07 at 14:02 +0100, Tom Conneely wrote:
> > On 5/7/05, Mystilleef <mystilleef gmail com> wrote:
> > > 1). Stop screensaver process
> > > 2). Restart screensaver process
> 
> The process is not needed really, my thoughts were (as I should have
> mentioned in my first post)
> 1. Stop/Disable Screensaver (though now I'm leaning towards Disable)
> then if screensaver is disabled unshade
> 2. Restart Screensaver
> 
> >...or implicitly enable the process when a screensaver is selected,
> >and disable it when no screensaver is selected.
> True, but users may wish to prevent the screensaver from locking the
> screen. e.g. when they want to walk away from the computer whilst its
> downloading a large file, but not have to unlock the screen everytime
> they want to check whether the download is complete. An alternative to
> disabling the screensaver, would be an option to disable the locking
> of the screen. any thoughts??
> ---
> tom.c
> _______________________________________________
> Usability mailing list
> Usability gnome org
> http://mail.gnome.org/mailman/listinfo/usability