After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 699494 - screen blank is very sudden
screen blank is very sudden
Status: RESOLVED DUPLICATE of bug 699112
Product: gnome-shell
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2013-05-02 16:58 UTC by William Jon McCann
Modified: 2013-05-02 21:49 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
video (567.68 KB, video/quicktime)
2013-05-02 16:58 UTC, William Jon McCann
Details

Description William Jon McCann 2013-05-02 16:58:41 UTC
Created attachment 243080 [details]
video

When I manually lock the screen we turn off the backlight. This is good. However the way we do it looks very unpolished. There are a couple reasons for this. The first is that the timing of the backlight going off is poorly sync'd with the lowering of the curtain. It seems to blank as soon as the curtain completes the fall. This isn't good because it links the two events but doesn't link them in a way that feels right. It would be better to either blank right away and skip the animation, allow the animation to complete and blank after "taking a beat", or to animate the blank and lowering at the same time.

In addition to this the backlight turns off very suddenly and this looks abrupt and discontinuous, and unpolished.

My recommendation is to:

 * Lower the shield with an animation (to provide feedback on the lock action)
 * Take a beat
 * Quickly animate the brightness to zero (just enough to round off the edge of the discontinuity)
Comment 1 Florian Müllner 2013-05-02 21:49:38 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 699112 ***