Bug 484177

Summary: Application specific Night Light allow/denylist
Product: [Applications] systemsettings Reporter: emeraldsnorlax
Component: kcm_nightcolorAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED INTENTIONAL    
Severity: wishlist CC: emeraldsnorlax, kwin-bugs-null, nate
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

Description emeraldsnorlax 2024-03-21 17:26:36 UTC
May be tangentially related to https://bugs.kde.org/show_bug.cgi?id=484023

When using a blue light filter and doing colour sensitive work, I'm forced to disable Night Light entirely across all displays, when what I really want is for it to only disable the filter on one application (e.g. Krita / Figma), while continuing to filter everything else. Right now, my only option is to disable it completely, which isn't really ideal. 

Additionally, sometimes I don't realise the filter is on at all, especially near sunset when it is gradually changing temperature, which can be problematic for colour sensitive work.

Some use cases:
- I'm playing a video game or watching a movie at night, and I have Discord or a web browser open on a second monitor
- I'm working on a project, and my text editor should stay filtered, but the preview and Figma should not be

What a perfect implementation would look like for me:
- Still scheduled to turn transition on at sunset, with denied windows never being filtered
- Denylist override ("filter everything, except these applications and windows")
- (I suppose some people may also want an allowlist mode, even though I wouldn't use it? "filter nothing, except these applications and windows")

tl;dr: Option to exclude certain windows from Night Light.
Comment 1 Nate Graham 2024-04-11 20:37:54 UTC
I can see the use case for this, but unfortunately disabling Night Light only for specific applications isn't technically feasible. We could conceivably make it possible to disable Night Light globally when certain apps start running, but is it really that hard to manually disable it for the duration of the work? It's a single middle-click on a visible System Tray icon. Not sure the effort-and-bug-burden-to-reward payoff there would be positive, sorry.