[gnome-screensaver] manager: fade out explicitly locks more quickly



commit 44edc03104f9757f4d866f24df8793f064b6ce70
Author: Ray Strode <rstrode redhat com>
Date:   Wed Jan 25 16:32:03 2012 -0500

    manager: fade out explicitly locks more quickly
    
    If the screensaver is explicitly asked to lock
    (as opposed to locking because of idle), then
    we should do it very quickly.  1 second is
    too long.
    
    This commit changes the fade to 60 steps per
    second and a quarter of second long
    (put another way, about 15 fade increments).
    
    https://bugzilla.gnome.org/show_bug.cgi?id=668551

 src/gs-fade.c    |    2 +-
 src/gs-manager.c |    2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
---
diff --git a/src/gs-fade.c b/src/gs-fade.c
index 24a3151..7a46879 100644
--- a/src/gs-fade.c
+++ b/src/gs-fade.c
@@ -693,7 +693,7 @@ static void
 gs_fade_start (GSFade *fade,
                guint   timeout)
 {
-        guint steps_per_sec = 30;
+        guint steps_per_sec = 60;
         guint msecs_per_step;
         struct GSFadeScreenPrivate *screen_priv;
         gboolean active_fade, res;
diff --git a/src/gs-manager.c b/src/gs-manager.c
index f658fc3..d42bd27 100644
--- a/src/gs-manager.c
+++ b/src/gs-manager.c
@@ -101,7 +101,7 @@ enum {
         PROP_ACTIVE,
 };
 
-#define FADE_TIMEOUT 1000
+#define FADE_TIMEOUT 250
 
 static guint         signals [LAST_SIGNAL] = { 0, };
 



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]