Marco Trevisan (Treviño) ab6a629955 screenShield: Compute lock timeout fade duration using animation settings ... When the screen is marked as idle, we normally start a fading animation and a timeout to finally lock the screen. This timeout is configured using the fade time if no longer delay is set in settings. However if animations are disabled or slowed-down/up, the fade time is different from the STANDARD_FADE_TIME and so we might end up showing the lock shield without actually locking for STANDARD_FADE_TIME in the disabled or slowed-up animations case, or locking too early in case of slowed-down animations. So, just adjust the timeout time using the same logic of animations so that this value is matching all the times. Related to https://gitlab.gnome.org/GNOME/gnome-shell/issues/1744 https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/749		2019-10-16 15:20:58 +00:00
..
extensionPrefs	cleanup: Use consistent brace style of blocks	2019-09-15 16:02:45 +02:00
gdm	loginDialog: Stop using deprecated actor property	2019-09-20 16:58:00 +00:00
misc	ibusManager: Cancel the preload engines timeout on clear	2019-10-02 18:19:53 +02:00
perf	cleanup: Disambiguate assignments in arrow functions	2019-09-15 16:02:45 +02:00
portalHelper	cleanup: Mark globals used from other modules as exported	2019-07-24 00:28:45 +02:00
ui	screenShield: Compute lock timeout fade duration using animation settings	2019-10-16 15:20:58 +00:00
js-resources.gresource.xml	accessibility: Add pointer accessibility support	2019-06-06 09:13:29 +02:00
meson.build	build: Use dedicated resources for helper programs	2018-08-14 17:28:04 +00:00
portal-resources.gresource.xml	build: Include params.js in portal-helper gresources	2018-10-23 15:38:31 +00:00
prefs-resources.gresource.xml	build: Use dedicated resources for helper programs	2018-08-14 17:28:04 +00:00