Bug 198316

Summary:	Text of disabled button doesn't appear as "disabled" on Qt apps when color scheme is used
Product:	[Frameworks and Libraries] kdelibs	Reporter:	hcoohb
Component:	qt	Assignee:	kdelibs bugs <kdelibs-bugs>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:

Description hcoohb 2009-06-29 19:09:01 UTC

Version:            (using KDE 4.2.4)
OS:                Linux
Installed from:    Fedora RPMs

When a different scheme color is set, the text of disabled buttons on Qt apps is no more disabled (the text appear as if the button was enabled).
This is only on Qt apps and no on kde apps.

How to reproduce :
- change color scheme in systemsettings and apply
- open an qt apps (ex: Arora) and see that text of disabled buttons is wrong (ex: in arora go on Windows>downloads>Clean up and then "clean up" should be disabled).

How to fix it :
I found a way of fixing it but I don't know if it is the proper.
Edit ~/.kde/share/config/kdeglobals and in the category [Colors:Button],
remove the line : ForegroundNormal=0,0,0

Indeed, a lot of scheme files have this line. I don't know what is the meaning of this line but it makes qt apps button wrongs !

I have seen that some of the scheme color files for 4.3 still have this line. Is the bug still present in 4.3? Because that would be awesome if it was fixed before the release.

Comment 1 hcoohb 2009-06-29 19:11:27 UTC

Actually, it is not in digikam, it is in kde global !
Sorry I made a mistake creating the bug report

Comment 2 Christoph Feck 2009-07-30 23:05:33 UTC

After some investigation, this turns out to be a Qt bug.

Qt first reads some base colors, then computes its palette from them (including correctly disabled colors).

However, after doing this, it reads some more KDE colors, including "Colors:Button/ForegroundNormal", and applies them to all color groups, without recomputing the disabled colors.

Comment 3 hcoohb 2009-07-30 23:41:38 UTC

Ok!

Should I report this bug on Qt task tracker then or you already did it ?

Comment 4 Christoph Feck 2009-12-09 22:02:40 UTC

This is fixed with Qt 4.6 and KDE 4.4. With the help of the new KDE plugin, Qt can use the KDE palette directly, without having to parse the configuration files.