diff options
author | Philipp Kerling <pkerling@casix.org> | 2017-06-23 15:59:53 +0200 |
---|---|---|
committer | Philipp Kerling <pkerling@casix.org> | 2017-06-27 09:33:33 +0200 |
commit | 677a46c988c719de2b4ee8ff316e2adfd56f9e59 (patch) | |
tree | c38b2a17866bab6394b4016607aee32700b319b6 /system | |
parent | 2bfa7ca6c3f14585122b0817edd1c43219e82633 (diff) |
Use new COSScreenSaverManager in Application
This changes the rules and functionality of the OS screen saver
inhibition to be more in line in with how modern desktop environments
work. Constant resetting of the screen saver is not necessary usually.
If it is, the platform-specific backend will have to implement it.
On desktop machines (that have an OS screen saver), the default should
be to use that. If the user then chooses to activate the Kodi screen
saver, this should completely override the OS screen saver as far as
permitted by the desktop environment. During video playback etc.,
the OS screen saver must always be inhibited regardless of whether
the Kodi screen saver is enabled.
In embedded environments (that do not have an OS screen saver), the
default should be to use the Kodi screen saver.
Diffstat (limited to 'system')
-rwxr-xr-x | system/settings/settings.xml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/system/settings/settings.xml b/system/settings/settings.xml index 918b208b4f..7efda42919 100755 --- a/system/settings/settings.xml +++ b/system/settings/settings.xml @@ -3348,7 +3348,7 @@ <group id="1" label="16000"> <setting id="screensaver.mode" type="addon" label="356" help="36130"> <level>0</level> - <default>screensaver.xbmc.builtin.dim</default> + <default>default</default> <!-- will be properly set on startup --> <constraints> <addontype>xbmc.ui.screensaver</addontype> <allowempty>true</allowempty> |