From 91545875f50bd58f48d1311355c8f0e4eef847e6 Mon Sep 17 00:00:00 2001 From: "bartfab@chromium.org" Date: Wed, 21 Nov 2012 13:58:27 +0000 Subject: Let chromeos::User decide whether the current session can be locked We have several different methods that try to determine whether the current session can be locked. This redundancy is difficult to maintain and has drifted out of sync in the past. The CL consolidates all checks and makes the chromeos::User class the autoritative source for whether the current session can be locked or not. BUG=152928 Review URL: https://chromiumcodereview.appspot.com/11412100 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@169031 0039d316-1c4b-4281-b951-d872f2087c98 --- ash/shell.h | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'ash/shell.h') diff --git a/ash/shell.h b/ash/shell.h index db4b5c0..c0be77b 100644 --- a/ash/shell.h +++ b/ash/shell.h @@ -210,6 +210,10 @@ class ASH_EXPORT Shell : internal::SystemModalContainerEventFilterDelegate, // Returns app list window or NULL if it is not visible. aura::Window* GetAppListWindow(); + // Returns true if a user is logged in whose session can be locked (i.e. the + // user has a password with which to unlock the session). + bool CanLockScreen(); + // Returns true if the screen is locked. bool IsScreenLocked() const; -- cgit v1.1