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

On Thursday 15 February 2007 18:34, Robert Knight wrote:
> One persistant offender is QTabWidget. =A0QTabWidget always has a border
> which cannot be turned off. =A0This border is appropriate in some cases,
> but leads to ugly results in others.

One thing that has been done in kde4 already is make the KPageDialog=20
automatically decide between having a tab and having a standalong widget.
This solves the problem of having a dialog with just 1 tab.

In fact; I think this is a good solution to a lot of the problems you state=
=2E I=20
hope you agree that the border is not a problem when there are multiple tab=
s.=20
And if that is the case we need a better way to remove the tabWidget when i=
ts=20
unneeded.

The problem you noted of altering the spacing between the border of the=20
tabWidget and the pageWidget is not a trivial one. You have to alter the=20
embedded widget which is not always a good idea. I'd like to avoid doing th=
at=20
so we can avoid having lots of corner cases...

So, my answer to your email is basically that we should not alter the=20
QTabWidget, but to have a simple way of removing the tabWidget from the=20
widget hierarchy if there are less than two tabs remaining.
=2D-=20
Thomas Zander

--nextPart4913954.WVF9YkWSIu
Content-Type: application/pgp-signature

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

iD8DBQBF1KOvCojCW6H2z/QRAiHTAJ4rIU3k38BtIFGdjsRecWUVqAMjQQCfS/Br
1/hlmEQKTi2LJVlh6cIU/TA=
=I1sR
-----END PGP SIGNATURE-----

--nextPart4913954.WVF9YkWSIu--