Jean-Marc Lasgouttes wrote:
"Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:

Abdelrazak> Please find attached the patch. The main problem with it
Abdelrazak> is that everything that is drawn in screen stays. So it
Abdelrazak> conflict with the background drawing that the kernel does
Abdelrazak> to erase something. If you manage to catch that background
Abdelrazak> cache command and send it to /dev/null, I think it is
Abdelrazak> possible to do something.

Is there a document that explains why QPicture should be faster? The
qt docs do not seem to imply that. Where did you get the idea?

The QPicture class "records" painting operations, it is similar to vector based painting (SVG or windows Meta file). So when you paint onto a QPicture it is not a real painting. The real painting happens when you "replay" the QPicture onto another pixmap oriented device. The fact that all painting operations happen in one go (during the update to the screen) is the winning factor here because the painting operation are "unified" first.

This is explained in the 4.1.3 documentation.

Abdel.

Reply via email to