On Friday 06 February 2009, Frédéric wrote:
Le 5/2/2009, Grissiom chaos.pro...@gmail.com a écrit:
I think you may try some CacheFlag or OptimizationFlag in QGraphicsView,
see:
http://www.riverbankcomputing.co.uk/static/Docs/PyQt4/html/qgraphicsview.h
tml#CacheModeFlag-enum
Le 6/2/2009, Jan Ekholm jan.ekh...@smultron.net a écrit:
At least don't use a thread to update GUI stuff, you'll just cause yourself a
lot of problems and crashes.
I finally found that the paint() method is very slow, and use all the
CPU. I re-designed my app so I don't have to use it (I just
I have had great success with QtGui.QGraphicsItemAnimation alleviating the same
issues that you are looking at.
It looks like that your PictureItem is returning a really large bounding box so
that caching system is repainting all or most of them at every step. Sometime
it helps in debugging
On Fri Feb 6 15:05:12 GMT 2009, Frédéric wrote:
I finally found that the paint() method is very slow, and use all the
CPU. I re-designed my app so I don't have to use it (I just draw
rectangles or ellipses, so I used the related items). And it is now very
fast.
I guess this tool would have
On vendredi 06 février 2009, dbod...@trolltech.com wrote:
I guess this tool would have been useful:
http://www.digitalfox.org/projets/qPyProfiler/
Maybe it will also help you track down any other performance issues you
encounter.
Thanks! I still need to optimize things, as refreshing the
Hello,
I draw some items (mainly rectangles or ellispes) on a scene, and it
seems to take a lot of resources, even with a few objects (say 10).
The main issue is on the maemo plateform, as Nokia N8x0 devices are not
that powerfull. Just drawing the initial scene takes a few seconds.
Are there
