[Interest] QDatastream, QMap, QImage serialization
Thiago Macieira
thiago.macieira at intel.com
Tue May 22 16:04:57 CEST 2018
On Tuesday, 22 May 2018 10:38:46 -03 Jason H wrote:
> > How about just using different function names instead? Like, you know,
> > "texture" and "textureImage"?
>
> How about texture() and texturePixmap()?
That is source-incompatible.
> There is a difference. As you already stated, a QPixmap requires more than
> a QImage, so what should be provided is a QImage,
Now think about how it's constructed internally.
QBrush only exists to paint, which means GUI (QPaintDevice is the basis of all
GUI). It is meant to paint efficiently. If QPixmap can do that more
efficiently, why should it store a QImage instead?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
More information about the Interest
mailing list