Using random wallpaper until user select one

chrome/browser/chromeos/login/user_manager_impl.h

Index: chrome/browser/chromeos/login/user_manager_impl.h
diff --git a/chrome/browser/chromeos/login/user_manager_impl.h b/chrome/browser/chromeos/login/user_manager_impl.h
index 22fab8665347c67a57d3f50ac95beb23c67b27d6..ecd16e08475bf09a71cfabf2a7e6862002fd8fb1 100644
--- a/chrome/browser/chromeos/login/user_manager_impl.h
+++ b/chrome/browser/chromeos/login/user_manager_impl.h
@@ -229,6 +229,9 @@ class UserManagerImpl : public UserManager,
   // mounting their cryptohomes using tmpfs.
   bool is_current_user_ephemeral_;
 
+  // Cache ephemeral user selected index in memory instead of local state.
+  int ephemeral_user_wallpaper_index_;

[Nikita (slow), 2012/03/26 15:31:58]

Do you think this may be moved somewhere to ash/* instead?

[bshe, 2012/03/26 16:12:10]

I can probably put it in ash/desktop_background/desktop_background_controller
with some plumbing work. I just thought it might be a good idea to put
everything user related to user_manager_impl. I didnt see similar cache pattern
used in this file though. I am wondering is there any particular reason why it
is not preferred? 

On 2012/03/26 15:31:58, Nikita Kostylev wrote:

[Nikita (slow), 2012/03/26 16:50:07]

I've thought that ash should have something like current wallpaper index but it
seems that it only has current wallpaper bitmap. And it doesn't make sense to
cache index in ash as it always is fetched from LocalState if needed. If we'd
have more such cases when we'll need to cache local_state data, we'll have to
provide some in memory storage.

+
   // Cached flag indicating whether ephemeral users are enabled. Defaults to
   // |false| if the value has not been read from trusted device policy yet.
   bool ephemeral_users_enabled_;