Bug 361257 - Colorscheme and other settings should not be copied into kdeglobals
Summary: Colorscheme and other settings should not be copied into kdeglobals
Status: RESOLVED MOVED
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR minor
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-31 23:05 UTC by Ivan Shapovalov
Modified: 2020-09-29 04:42 UTC (History)
1 user (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Ivan Shapovalov 2016-03-31 23:05:33 UTC 
Currently, when one selects a KDE color scheme in systemsettings, it effectively has its contents _copied_ into kdeglobals. Instead, the color scheme name in [General]/ColorScheme could be used to lookup the color scheme file and read it in run-time, but it isn't so.

This is scripting-unfriendly.

Reproducible: Always

Steps to Reproduce:
1. Set a non-default color scheme via systemsettings
2. Open kdeglobals in editor, remove all sections like [ColorEffects:*], [Colors:*], [DesktopIcons], [DialogIcons] (but not [General])
3. Open any application

Actual Results:  
Default color scheme is used.

Expected Results:  
Color scheme is looked up using [General]/ColorScheme config key, read in runtime and applied
Comment 1 Nate Graham 2020-09-29 04:42:53 UTC 
Yes, this causes various problems. Let's discuss ie in the Phabricator task I opened about it recently: https://phabricator.kde.org/T13663