Bug 305350

Summary:	visited color can not be changed persistently
Product:	[Applications] systemsettings	Reporter:	Martin Koller <martin>
Component:	kcm_colors	Assignee:	Matthew Woehlke <mwoehlke.floss>
Status:	RESOLVED FIXED
Severity:	normal	CC:	cfeck
Priority:	NOR
Version First Reported In:	4.9.0
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:	http://commits.kde.org/kde-workspace/61349942ae3c84f6010a4913891b07d5bbc34e10	Version Fixed/Implemented In:	4.9.1
Sentry Crash Report:

Description Martin Koller 2012-08-17 20:03:48 UTC

I open the colors kcm module (kcmshell4 colors), select the colors tab and chanhe the color of "visited text" from my current #FFA4F0 to e.g. #FF8000 and click OK.
The next time I open the colors module again and look in the colors tab, the "visited text" is again the old color.

Reproducible: Always

Comment 1 Christoph Feck 2012-08-18 00:38:51 UTC

https://git.reviewboard.kde.org/r/106066/

Comment 2 Christoph Feck 2012-08-21 19:13:02 UTC

Git commit 61349942ae3c84f6010a4913891b07d5bbc34e10 by Christoph Feck.
Committed on 21/08/2012 at 21:09.
Pushed by cfeck into branch 'KDE/4.9'.

Fix multiple issues in colors KCM

- do not offer "Current" (or "Default") name for saving
- update preview icon when a colors gets changed
- write "Current" as scheme name, when the temporary theme is used
- upon loading the "Current" scheme, mark it as "needs saving"
- update preview icon for "Current" scheme when it is applied

See review description for details.

REVIEW: 106066
FIXED-IN: 4.9.1

M  +12   -1    kcontrol/colors/colorscm.cpp

http://commits.kde.org/kde-workspace/61349942ae3c84f6010a4913891b07d5bbc34e10