<!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>
> > Pixmaps reside on the xserver and are fast to paint over and over again<br>
> > Images reside on the client and are good if you need to poke at the<br>
> > pixels or change it every time you display it<br>
This is not always true. This is currently true, on linux if you use the default engine "native", but if you use "raster" QPixmap are treated as a qimage, and they use the X Shared Memory extension to make cheap copy with a XPimap [1] (not sure about the GL engine, but I would suspect that are stored as textures).<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>> There is also the difference between xrender capable systems and<br>
> non-xrender capable systems. If I remember correctly, we use QImage by<br>
> preference, but if xrender isn't available, we use QPixmap.<br>
Maybe for Qt4.6 when the raster engine is considered more stable, it will be worth to replace this by an option to switch to the "raster" engine and clean our code.<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>[1] http://labs.trolltech.com/blogs/2008/10/22/so-long-and-thanks-for-the-blit/<br>
-- <br>
Cyrille Berger</p></body></html>