From kde-commits  Wed Dec 31 15:44:13 2008
From: Rafael =?iso-8859-15?q?Fern=E1ndez_L=F3pez?= <ereslibre () kde ! org>
Date: Wed, 31 Dec 2008 15:44:13 +0000
To: kde-commits
Subject: Re: KDE/kdelibs/kdeui/widgets
Message-Id: <200812311644.15170.ereslibre () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-commits&m=123073829730887
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart1331961.r9BQIPGL99"

--nextPart1331961.r9BQIPGL99
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,

> Your commit was in klineedit.cpp
> (r902990)

Ah, OK, this thread is about kcompletionbox...

The most important change on that commit is here:

( keycode.unicode()->category() !=3D QChar::Symbol_Modifier || txt !=3D old=
_txt )=20
)

Basically, it is possible to have pressed a key (for being more exact,=20
released a key, since there seems Qt has a bug, it won't trigger keyPressEv=
ent=20
but twice keyReleaseEvent if pressed '=E1', for instance) and don't need to=
=20
write something, this means: =E1, =E9, =ED, =F3, =FA in spanish. You type '=
'' but=20
nothing will be written till you hit later 'a', 'e', 'i', 'o' or 'u'.

The old_txt approach was being used before but in a more local case (not be=
ing=20
an attribute).

I don't see why would this break MMB or RMB use case. Can you provide me an=
=20
example, please ?


Regards,
Rafael Fern=E1ndez L=F3pez.

--nextPart1331961.r9BQIPGL99
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

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

iEYEABECAAYFAklbk00ACgkQck5Abj8B0HCYfACfQt2/8l5LI7LfKGDLTz0Xxmul
bV8AoLdgQuhXSUikPOaT96aW5jtsUTqj
=sGFZ
-----END PGP SIGNATURE-----

--nextPart1331961.r9BQIPGL99--