-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE REQ] being consistent with KDE settings #258
Comments
Hi! |
I suggest an easy way with KDE. By default, don't switch off the screen, let KDE manage the feature “screen energy saving “switch off the screen after a delay”” That's all. KDE is a poor tool to manage the screen. For “suspend to ram or disk” I assume this is the OS which manages these features and switch off the screen. |
Yep but then all the people using Clight in a simpler environment (like no DE at all, just wm), would have to tinker with Clight conf file; i don't like that from an UX perspective.
Note that Clight does not manage Suspend, it just manages DPMS (that is different, it just switches off the screen but does not suspend the system). |
Note however that i am not that convinced about this feature; it is disruptive for people that today run Clight with default settings on DEs. |
I am going to close this one; i think it is out of scope for Clight (i am spring-cleaning issues :D ) |
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
KDE manages :
All these features are enabled by default, excepted "Night Color" which requires a user action.
To be consistent with KDE, when installing Clight or running Clight, it is necessary to disable KDE features if Clight gets the same one.
Also it is consistent for Clight :
Why ?
The consistency must be handled by Clight not the user because the user is mainly not a techie person.
Thanks for your attention.
The text was updated successfully, but these errors were encountered: