[PyQt] QtSvg.QSvgRenderer.boundsOnElement issue

[Aron Bierbaum]

Thanks for the quick turn around.

-Aron

On Mon, Apr 27, 2009 at 2:37 PM, Phil Thompson
<phil at riverbankcomputing.com> wrote:
> On Mon, 27 Apr 2009 11:38:40 -0500, Aron Bierbaum <aronbierbaum at gmail.com>
> wrote:
>> I have recently downloaded and testing with the latest PyQt 4.5
>> snapshot, 20090426, and I am having a few problems. If I run the
>> attached test program with PyQt 4.4.4 and Qt 4.5.0 I get the correct
>> output:
>>
>> Square 1 bounds: PyQt4.QtCore.QRectF(10.000000720000001,
>> 942.36217671999998, 100.00000056, 100.00000055999999)
>> Square 2 bounds: PyQt4.QtCore.QRectF(119.99999839, 832.36216838999997,
>> 99.999998219999981, 99.999998220000066)
>> Square 3 bounds: PyQt4.QtCore.QRectF(230.00000691, 942.36218690999999,
>> 100.00000317999999, 100.00000318000002)
>>
>> But if I run with Qt 4.5.0 and the latest PyQt 4.5 snapshot I get
>> empty QRects for all bounds:
>>
>> Square 1 bounds: PyQt4.QtCore.QRectF(0.0, 0.0, 0.0, 0.0)
>> Square 2 bounds: PyQt4.QtCore.QRectF(0.0, 0.0, 0.0, 0.0)
>> Square 3 bounds: PyQt4.QtCore.QRectF(0.0, 0.0, 0.0, 0.0)
>>
>> I have looked at the changes between the two versions, and I can't see
>> anything that would cause this to happen. Am I the only one that is
>> seeing this? Does anyone have any ideas on what could be going wrong?
>
> It's caused by me reordering some methods that means the filename you are
> passing is being interpreted as the SVG data.
>
> Tonight's snapshot will revert those changes - and (hopefully) properly
> fixes the original problem.
>
> Thanks,
> Phil
>