From kde-core-devel  Tue May 30 11:27:33 2006
From: Thomas Zander <zander () kde ! org>
Date: Tue, 30 May 2006 11:27:33 +0000
To: kde-core-devel
Subject: KSelectAction bugs
Message-Id: <200605301327.33932.zander () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=114898856018500
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart9827254.9PaNIV3Kks"

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

Not sure where to post this; but in KWord I noticed these issues (using=20
the snapshot);

=2D doing a setItems(QStringList) on the action in response to a signal=20
coming from that same action I get a crash.
Aaron looked into this briefly; but I'm not sure if that lead to a fix.=20
issue was that clear() was called, deleting the action we are currently=20
executing.
Doing a deleteLater instead failed to actually remove the action from the=20
KSelectAction itself, leading to more and more entries in the combobox.

=2D the combobox on the toolbar does not work; it gets filled but changing=
=20
it has no effect and changing the selected item in the action does not=20
alter the combobox.

=2D connecting to SIGNAL( triggered( const QString & ) will give me the tex=
t=20
as its in the menu, not the text of the action.  This has the effect that=20
when kdelibs added shortcuts I get a '&foo' instead of a 'foo' passed.

=2D-=20
Thomas Zander

--nextPart9827254.9PaNIV3Kks
Content-Type: application/pgp-signature

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

iD8DBQBEfCwlCojCW6H2z/QRAq9uAKCOw86vZqS4Hgqs2qPIPCv/feE3LgCeM8/r
v5IY29PsRHAucS5C2kKNH/Y=
=mnZR
-----END PGP SIGNATURE-----

--nextPart9827254.9PaNIV3Kks--