Bug 361257

Summary:	Colorscheme and other settings should not be copied into kdeglobals
Product:	[I don't know] kde	Reporter:	Ivan Shapovalov <intelfx>
Component:	general	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED MOVED
Severity:	minor	CC:	nate
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

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