Bug 460394

Summary: Let the "Application handles its own scaling" setting be per-application
Product: [Plasma] kwin Reporter: alphaproject217
Component: wayland-genericAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED INTENTIONAL    
Severity: wishlist CC: kde2, kde, nate, stephenackerman16
Priority: NOR    
Version First Reported In: git-stable-Plasma/5.26   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description alphaproject217 2022-10-13 22:28:04 UTC
SUMMARY

The reason I switched to KDE wayland, despite it's shortcomings, is because of the staggering amount of applications that have no support for a DPI other then 96, as well as X11's shortcomings with multi-monitor setups (I like being able to set my second monitor to it's proper resolution while retaining the DPI it should have)

On that note, I'm also quite annoyed with applications being blurry. Ideally, it's arguable whether smooth scaling even needs to be used because some of these applications would actually look better using nearest neighbor scaling, but I digress: I think that the newest feature that lets you let applications handle scaling themselves is a welcome addition. But as I said earlier, some applications do not do this correctly. So while I hate the default scaling, it's actually a necessity for many programs...and yet, not others.

Alls this to say, I think that the "let programs handle their own scaling" option should be offered on a per application basis.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5-15-73-1-MANJARO
KDE Plasma Version: 5.26.0
KDE Frameworks Version: 5.99.0
Qt Version: 5.15.6
Comment 1 Nate Graham 2022-10-28 19:31:23 UTC
*** Bug 461061 has been marked as a duplicate of this bug. ***
Comment 2 David Edmundson 2023-01-24 12:02:39 UTC
We can't.
Comment 3 Nate Graham 2023-01-24 16:13:42 UTC
Well, we can: by spinning up a new XWayland instance per app. But it's technically challenging, involves risk, and wastes system resources.