Drawing on a QPicture should update its bounding rect. Like this:
>>> picture = QPicture() >>> painter = QPainter(picture) >>> picture.boundingRect() QRect(0,0,0,0) >>> painter.drawRect(20,20,50,50) >>> picture.boundingRect() QRect(20,20,50,50)
But if I draw text on it, the bounding rect isn’t updated:
>>> picture = QPicture() >>> painter = QPainter(picture) >>> picture.boundingRect() QRect(0,0,0,0) >>> painter.drawText(10,10, 'Hello, World!') >>> picture.boundingRect() QRect(0,0,0,0)
Obviously, it doesn’t update the bounding rect.
Is there a way to make it repsect drawn text or do I have to do it manually? (Not too hard, but I hope that Qt can assist me here.)
Take a look at these overload methods, where you must specify the Bounding Rectangle after the text parameter (which is apparently different than the rectangle in the first argument’s position):
QPainter.drawText (1), QPainter.drawText (2)
Update:
It appears if you want to generate a bounding rectangle for the drawText() method in advance, you just call the boundingRect() method on QPainter, which does the following:
QPainter.boundingRect
I linked to BoundingRect with QRectF output, but the information applies to the other versions as well.
So basically, pass the result of QPainter.boundingRect() into the boundingRect parameter of the QPainter.drawText() method (the second QRect argument).
Update 2:
I APOLOGIZE PROFUSELY for being so damn dense. I forgot that drawText works differently in PyQt than in Qt. The bounding rectangle is RETURNED by the drawText function (not passed in like Qt) and in addition, you have to specify alignment flags before you get a bounding rectangle given back to you. (I even included the p.end() as per Aaron Digulla’s comment):
Here is the output:
So it appears you will have to set the bounding rectangle yourself, though at least it is returned to you by the output of the drawText() method when passing in flags.
This does not seem like ideal behaviour, that you would have to set the bounding rectangle yourself. I hope someone else has the answer you’re looking for, but I suspect you may want to report this bug.