From kde-core-devel  Thu Sep 20 11:44:10 2007
From: Thomas Zander <zander () kde ! org>
Date: Thu, 20 Sep 2007 11:44:10 +0000
To: kde-core-devel
Subject: Re: Temporary KColorScheme change - hard-code some state colors
Message-Id: <200709201344.10293.zander () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=119028868221882
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart3308090.XG9JIW8508"


--nextPart3308090.XG9JIW8508
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Monday 17 September 2007 14:16:56 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.

Let me correct the statement from Richard at the top;  using the inactive=20
color palette for whole applications is broken by design.
There are lots of reasons for this, for example the window managers don't=20
allow us to group windows together to mark them as a group.  Which is=20
needed so the dockwidget (/helper window) is not marked as deactivated=20
when focus moves to the mainwindow.

=46or that reason alone Oxygen doesn't have a chance to do this correctly.

As I stated in another thread; this stuff was designed to do things like=20
change the selection color. And if you use it differently you can run=20
into problems. If these problems are actual bugs is then open for=20
interpretation :)
=2D-=20
Thomas Zander

--nextPart3308090.XG9JIW8508
Content-Type: application/pgp-signature

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

iD8DBQBG8l0KCojCW6H2z/QRAgghAJ9ZFhyzdfYTDLHjGmdpnztfjFLTzwCgq2Tg
Ow0Nck4Z/G2o5hkCb3DMlMs=
=F4Gy
-----END PGP SIGNATURE-----

--nextPart3308090.XG9JIW8508--