Merge lp:~osomon/oxide/applicationstatechanged into lp:~oxide-developers/oxide/oxide.trunk
Proposed by
Olivier Tilloy
Status: | Merged | ||||
---|---|---|---|---|---|
Merged at revision: | 863 | ||||
Proposed branch: | lp:~osomon/oxide/applicationstatechanged | ||||
Merge into: | lp:~oxide-developers/oxide/oxide.trunk | ||||
Diff against target: |
378 lines (+173/-13) 9 files modified
qt/core/browser/oxide_qt_browser_platform_integration.cc (+17/-1) qt/core/browser/oxide_qt_browser_platform_integration.h (+8/-1) qt/core/core.gyp (+6/-0) shared/browser/oxide_browser_platform_integration.cc (+23/-0) shared/browser/oxide_browser_platform_integration.h (+18/-0) shared/browser/oxide_browser_platform_integration_observer.cc (+30/-0) shared/browser/oxide_browser_platform_integration_observer.h (+37/-0) shared/browser/oxide_power_save_blocker.cc (+32/-11) shared/shared.gyp (+2/-0) |
||||
To merge this branch: | bzr merge lp:~osomon/oxide/applicationstatechanged | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Chris Coulson | Approve | ||
Review via email: mp+241789@code.launchpad.net |
Commit message
Monitor application state changes, and update PowerSaveBlocker state accordingly
(remove the screen dim lock when the app goes into the background, and restore it when it comes to the foreground).
To post a comment you must log in.
Thanks for this. I've added a couple of comments inline.
Also, I wonder whether it would be better to drop the state argument from the notification and add a BrowserPlatform Integration: :GetApplication State() instead. There's always the possibility of a PowerSaveBlocker being created inbetween the notification firing and the application being stopped.