diff options
| author | wez@chromium.org <wez@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-04-03 05:34:27 +0000 |
|---|---|---|
| committer | wez@chromium.org <wez@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-04-03 05:34:27 +0000 |
| commit | 6aaebcff037f6f9310d1041c51df7e612e68affe (patch) | |
| tree | 9d69ab7b6eee613c6d8d1d599a357cc017553849 /content/renderer/render_widget_fullscreen_pepper.h | |
| parent | 4716cc3d49eb12d5f54157f2cf4efe5ec2684233 (diff) | |
| download | chromium_src-6aaebcff037f6f9310d1041c51df7e612e68affe.zip chromium_src-6aaebcff037f6f9310d1041c51df7e612e68affe.tar.gz chromium_src-6aaebcff037f6f9310d1041c51df7e612e68affe.tar.bz2 | |
Ensure display hardware is powered up during Chromoting sessions.
This CL uses SetThreadExecutionState to:
* Re-set the display suspend timeout before every capture.
* Re-set the system idle timeout before every input injection.
The latter is not generally very useful, since it really only affects hosts configured to power-down when idle, at which point the host won't be accessible anyway, but it does mean that such a host could be powered-up manually and then used via Chromoting, without it powering down mid-session.
BUG=120429
TEST=Configure a Windows system with a very short display timeout, and display power-saving, and connect to a host running on it. Upon connection the display should power on and the host should be usable.
Review URL: http://codereview.chromium.org/9968071
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@130321 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content/renderer/render_widget_fullscreen_pepper.h')
0 files changed, 0 insertions, 0 deletions