https://bugs.kde.org/show_bug.cgi?id=511346
Bug ID: 511346
Summary: Use both Qt and platform API in KColorSchemeWatcher
Classification: Frameworks and Libraries
Product: frameworks-kguiaddons
Version First 6.18.0
Reported In:
Platform: Other
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Right now, KColorSchemeWatcher has four backends that are decided compile time:
1. mac
2. qt
3. win
4. xdg
I propose to always compile the Qt backend, even if the platform backend is
available. First try the value from the platform backend, if it has no
preference, fall back to the Qt value (or the other way around?).
I'm not sure thhough whether win and mac backends have any sense nowadays as Qt
supports querying those platforms' color scheme for a long time...
This way, the code will work even on the Linux systems having portals
unconfigured if the user has a Qt platform theme plugin supporting the
QPlatformTheme::colorScheme API, providing the potential to work correctly for
minimal WM setups using qt6ct, gtk3 and etc. Even LXQt doesn't seem to provide
color scheme via portal as of now.
This is related to https://bugs.kde.org/show_bug.cgi?id=496174 and
https://bugs.kde.org/show_bug.cgi?id=492593.
--
You are receiving this mail because:
You are watching all bug changes.
