On terça-feira, 21 de fevereiro de 2012 15.40.16, jan-arve.saet...@nokia.com wrote: > Sorry for top-posting from my N9... > > > I was thinking the same, but I'm afraid we can't change it, since it would > cause too many subtle bugs.
> The best thing I can think is to deprecate it, and add a QRectS or QRectI,
> but I'm not utterly convinced...
We could deprecate QRect and QRectF, and introduce a proper QRectangle. It
should be doable by means of an implicit QRect(const QRectangle<int> &)
constructor and an operator QRectangle<int>() const.
If that doesn't work, it would unfortunately mean deprecating all of the API
that uses QRect and QRectF and add new API.
But by the same token that Andreas has of subtle bugs, this change would
introduce subtle bugs in Qt code that relies on the quirky QRect behaviour.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
