endless loop in KDoubleNumInput (with patch)
Matthias Kretz
kretz at kde.org
Fri Nov 15 14:02:19 GMT 2002
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thursday 14 November 2002 19:01, Dirk Mueller wrote:
> On Mit, 13 Nov 2002, Matthias Kretz wrote:
> > calling KDoubleNumInput::setRange may cause an endless loop if
> > d->spin->setRange changes the value of the spinbox. Because that
> > automatically changes the value of the slider which in turn changes the
> > value of the spinbox ... and so forth.
>
> spin->setRange should block signals then.
But what about those who rely on the signal
KDoubleNumInput::valueChanged(double) being emitted on range change? Granted,
I don't know if that's important, but nevertheless it could be the source for
bugs, no?
- --
C'ya
Matthias
________________________________________________________
Matthias Kretz (Germany)
http://Vir.homeip.net/
MatthiasKretz at gmx.net, kretz at kde.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD4DBQE91P53yg4WnCj6OIoRAq/WAJiYqt9+W6F5Ir/8UjBa+/DW2XrFAJ42xziD
92CrlBmvLABn1EIiRKvl8Q==
=psxz
-----END PGP SIGNATURE-----
More information about the kde-core-devel
mailing list