[gnome-shell] unlockDialog: Use "normal" background
- From: Florian Müllner <fmuellner src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gnome-shell] unlockDialog: Use "normal" background
- Date: Fri, 21 Feb 2020 12:43:49 +0000 (UTC)
commit 0afac367135d3e1a6eef3c86c6e7f1dcfc339ece
Author: Florian Müllner <fmuellner gnome org>
Date: Thu Feb 13 23:16:38 2020 +0100
unlockDialog: Use "normal" background
Now that we apply a strong blur effect to the background, it doesn't
make too much sense to use a separate lock-screen background: It will
be mostly unrecognizable anyway.
The alternative would be to turn off the blur effect if a different
background is used (or have a hidden setting for that), but that would
then imply that we must keep the contents readable without blur.
Let's avoid that rabbit hole and just re-use the regular background.
https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/1001
js/ui/unlockDialog.js | 3 ---
1 file changed, 3 deletions(-)
---
diff --git a/js/ui/unlockDialog.js b/js/ui/unlockDialog.js
index 7f33e68e12..5a3d24fd22 100644
--- a/js/ui/unlockDialog.js
+++ b/js/ui/unlockDialog.js
@@ -18,8 +18,6 @@ const IDLE_TIMEOUT = 2 * 60;
// The timeout before showing the unlock hint (in seconds)
const HINT_TIMEOUT = 4;
-const SCREENSAVER_SCHEMA = 'org.gnome.desktop.screensaver';
-
const CROSSFADE_TIME = 300;
const FADE_OUT_TRANSLATION = 200;
const FADE_OUT_SCALE = 0.3;
@@ -624,7 +622,6 @@ var UnlockDialog = GObject.registerClass({
container: widget,
monitorIndex,
controlPosition: false,
- settingsSchema: SCREENSAVER_SCHEMA,
});
this._bgManagers.push(bgManager);
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]