From 5201a35272a58e286e9724b0481ad706c391404a Mon Sep 17 00:00:00 2001 From: Ruakij Date: Sat, 30 Jul 2022 17:32:00 +0200 Subject: [PATCH] Update description and install instructions --- README.md | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 935bfcb..5a0e1e0 100644 --- a/README.md +++ b/README.md @@ -32,7 +32,11 @@ This script aims to fix this. Adding a script to `notifyrc` as event makes it possible to change settings when screen-locking begins. -So after x seconds the screen will simply be forcefully turned off using `xset`. +When the screen is locked, the script will change the screen-timeout to a custom-value in the config `~/.config/powermanagementprofilesrc` (or a default of 10s). + +This is done, so even after the System wakes up and activates the screens e.g. when mouse is moved, but no unlock is done, the screen begins to sleep quickly again. + +After a successful unlock, the value from the config is reapplied.
@@ -40,4 +44,10 @@ So after x seconds the screen will simply be forcefully turned off using `xset`. Place the file `event_screensaver` to a bin-location, for a local user this is typically `~/.local/bin/` and make it executeable. -In Settings under `Notifications > Applications > Configure > 'Screen Saver' > Configure Events...` for event `Screen locked`, enable `Run command` and add your script-location for `event_screensaver`. +In Settings under `Notifications > Applications > Configure > 'Screen Saver' > Configure Events...` for event locked & unlocked, enable `Run command` and add your script-location for `event_screensaver` and the event triggered. + +Example: +``` +Screen locked +Run Command: ~/.local/bin/event_screenSaver locked +```