From kde-core-devel  Mon Sep 17 16:56:58 2007
From: "Aaron J. Seigo" <aseigo () kde ! org>
Date: Mon, 17 Sep 2007 16:56:58 +0000
To: kde-core-devel
Subject: Re: Temporary KColorScheme change - hard-code some state colors
Message-Id: <200709171057.02545.aseigo () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=119004826910033
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart3239472.hWtvinvh4m"

--nextPart3239472.hWtvinvh4m
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Monday 17 September 2007, Richard Dale wrote:
> On Monday 17 September 2007, pinheiro wrote:
> > > No, the hack to use the inactive control color palette for entire
> > > windows is just broken and can never be made to work properly.
> >
> > Plese explain me how come? sory coding is not my experties.
>
> The active/inactive palette api and visual appearance is designed for
> showing enabled/disabled controls within a window. Hence, text becomes

it also messes with the appearance of things like the debugging toolbox in=
=20
plasma that currently appears on mouse hover; the entire thing is greyed ou=
t=20
until you actually click on one of the widgets. this is certainly not the=20
expected or desired behaviour. forcing it to be the currently active widget=
=20
when it slides out would cause other side-effects, so i don't want to do th=
at=20
either... =3D/

=2D-=20
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Trolltech

--nextPart3239472.hWtvinvh4m
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBG7rHe1rcusafx20MRAtVDAJ43WIPJqT38D9GrqMET9QuQiXoSFQCfZQw0
pJsJ61JwwG0n7d3kw3RoTG8=
=UlRM
-----END PGP SIGNATURE-----

--nextPart3239472.hWtvinvh4m--