Bug 481923 - Feature request: Add a 'paper' reading mode to reduce eyestrain
Summary: Feature request: Add a 'paper' reading mode to reduce eyestrain
Status: RESOLVED INTENTIONAL
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_nightcolor (other bugs)
Version First Reported In: unspecified
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-02-28 10:38 UTC by Jondo
Modified: 2024-02-29 18:57 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
The settings in a MIUI 12 device. Unfortunately I did not find a picture where you can actually see the texture. (128.68 KB, image/png)
2024-02-28 10:38 UTC, Jondo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jondo 2024-02-28 10:38:45 UTC
Created attachment 166152 [details]
The settings in a MIUI 12 device. Unfortunately I did not find a picture where you can actually see the texture.

SUMMARY
It would be great to have a 'paper' reading mode that adds a coarse paper-like texture to backgrounds to all elements on the screen, making it look like an E ink display. The mode is available on newer Xiaomi devices to reduce eyestrain when reading.

STEPS TO HAPPINESS
1. I guess the night color settings would be a good place for such a mode but would be happy with any place obviously.
2. While have no insights into this kind of programming I hope it could be a minor tweak. 
3. Thanks in advance.

OBSERVED RESULT
Reduced eyestrain and increased happiness.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Leap 15.5
(available in About System)
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Comment 1 Nate Graham 2024-02-29 18:57:43 UTC
Night Light already switches to warmer colors, but I'm afraid adding a textured paper background is something that's not feasible. It would need to either be done as a KWin effect (which would be error-prone and not universal) or implemented in every app (which is not feasible), As a result it would end up as a "broken promise" feature and we'd get endless bug reports about it not applying to this app or that app. So I don't think we'll be able to do this, sorry!