| Summary: | There should be a tool to fetch "ideal" compositing settings for a given hardware/driver | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Thomas Lübking <thomas.luebking> |
| Component: | compositing | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | wishlist | CC: | xaver.hugl |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Thomas Lübking
2014-08-08 12:20:29 UTC
interesting idea. Would you want it to write the configuration settings or change the default values in the configuration settings and adjust the heuristics in GLPlatform? This could also be used to prevent stupid things like EGL not supported on NVIDIA... Rewrite the local config.
There's no point in adjusting defaults and have them trumped by the users broken config.
The scenario is "I'm just a user and don't know 90% of the terms in this kcm, I've tried a lot and just want animations & shadows to work, 'key?"
So when the user presses that button and the download indicator finished and kwin eventually restarted, he should be faced with a config confirmed "good" by others.
Alternatively we'd have to strip the local config anyway and then evtl. deal w/ write permissions on the local defaults - and if you think about several users you've also to expect several GPUs (*real* multihead) or preferences ("I don't care whether GL compositing is a sane default for my daughter, it breaks my CAD" or whatever)
Drivers are in a good enough state now that I don't think we need anything like this anymore |