<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" /><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" font-family:'DejaVu Sans'; font-size:9pt; font-weight:400; font-style:normal;">On Wednesday 22 July 2009, Boudewijn Rempt wrote:<br>
> On Wed, 22 Jul 2009, Cyrille Berger wrote:<br>
> > On Wednesday 22 July 2009, Boudewijn Rempt wrote:<br>
> > > > Pixmaps reside on the xserver and are fast to paint over and over<br>
> > > > again Images reside on the client and are good if you need to poke at<br>
> > > > the pixels or change it every time you display it<br>
> ><br>
> > This is not always true. This is currently true, on linux if you use the<br>
> > default engine "native", but if you use "raster" QPixmap are treated as a<br>
> > qimage, and they use the X Shared Memory extension to make cheap copy<br>
> > with a XPimap [1] (not sure about the GL engine, but I would suspect that<br>
> > are stored as textures).<br>
><br>
> Just to make sure: I didn't write what you quoted :-). Another difference<br>
> is that QPixmap, afaik, doesn't have transparency, which QImage has.<br>
sure QPixmap can have transparency. But it's backend/system dependent, for instance, if you use 'native' and don't have Xrender then it ignores the transparency.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>-- <br>
Cyrille Berger</p></body></html>