From kde-core-devel  Tue Feb 26 15:33:43 2002
From: Scott Wheeler <scott () slackorama ! net>
Date: Tue, 26 Feb 2002 15:33:43 +0000
To: kde-core-devel
Subject: QClipboard and QLineEdit
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=101473779427170

In QLineEdit at the moment, it appears that QClipboard::dataChanged() is=20
(logically) connected to QLineEdit::clipboardChanged().  However this=20
presents a problem because QLineEdit::clipboardChanged() contains a=20
deselect().  So, if arbitrary data is to be put into the clipboard by=20
setData() or setText(), this causes the selection in a QLineEdit instance=
 to=20
be deselected.

It seems that because of the difference in selection and clipboard, that =
only=20
a QClipboard::selectionChanged() signal should cause a deselect.

At the moment, this causes a problem with Klipper in KDE CVS.  In a mode =
that=20
tries to synchronize the selection and the clipboard, Klipper polls=20
applications for the selection and calls QClipboard::setText() with the=20
result.  Unfortunately, in QLineEdit instances, this causes the selection=
 to=20
be deselected, which as you can imagine, can be quite annoying.

Thanks!

-Scott=20