QGraphicsScene/QGraphicsView performance

onurozcelik

[quote author="zgulser" date="1297760455"]Finally, what's the renderer?
[/quote]

QSvgRenderer instance pointer.

onurozcelik

[quote author="Jorj" date="1297696052"]you are emitting signals during your paint method, if these are connected to the (im assuming) game logic, and trigger a redraw, you will get an infinite ish loop[/quote]

I commented emit stuff but CPU usage did not change.

zgulser

Ok.

I think you should do all other controlling stuff outside the paint method( I bet you know signal-slot issue) and just perform renderer->render(painter,boundingRect()); in it.

MarekR22

As I can see now you mess up everything with everything.

paint method should do only painting nothing else (performance reasons)
sizeHint is hardcoded I doubt you reale need this
boundingRect is wrong for sure.
you messing around with properties when it is not needed (this is needed if code supposed to manipulate objects with unknown api/structure).

Maybe explain what this should show!

[EDIT: fixed list - use "*" instead of "-" as "bullets", Volker]

onurozcelik

MarekR22

How should I implement boundingRect()?
Sample code please.

zgulser

Although it won't solve your problem totally, it should be something like;

@

void Item::setBoundingRect(const QRect& pBoundingRect)
{
mBoundingRect = pBoundingRect;
}

const QRect& Item::getBoundingRect()
{
return mBoundingRect;
}

const QRect& Item::boundingRect()
{
return getBoundingRect();
}
@

ivan

You could also cache the svg render output to a pixmap.

MarekR22

[quote author="onurozcelik" date="1297780179"]MarekR22

How should I implement boundingRect()?
Sample code please.[/quote]
The joke is that you don't have to. QGraphicsWidget returns boundingRect which in most cases should be ok.
But like I said describe what you are trying to achieve then we will show you how code should look like.
Note there is a class "QGraphicsSvgItem":http://doc.trolltech.com/latest/qgraphicssvgitem.html. Maybe this is enough for you.

onurozcelik

implementing boundingRect correctly solved the infinite repaint loop problem.

andre

[quote author="zgulser" date="1297781851"]
Although it won't solve your problem totally, it should be something like;

@

void Item::setBoundingRect(const QRect& pBoundingRect)
{
mBoundingRect = pBoundingRect;
}

const QRect& Item::getBoundingRect()
{
return mBoundingRect;
}

const QRect& Item::boundingRect()
{
return getBoundingRect();
}
@[/quote]

For performance critical code, you should just inline the stuff above.