On 2/23/07, <b class="gmail_sendername">Michael Guntsche</b> <<a href="mailto:mike@it-loops.com">mike@it-loops.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>On Feb 23, 2007, at 17:51, Arve Knudsen wrote:<br><br>> Hello<br>> If I try to reimplement the method drawItems in a QGraphicsScene<br>> subclass, the program segfaults. Is this a bug in PyQt? I am by the<br>
> way using PyQt 4.1.1 (self-compiled) and Qt 4.2.0 (Ubuntu). I've<br>> included a sample program which exhibits the behaviour.<br>><br><br>Works here.<br>QT 4.2.2 and the latest Pyqt snapshot.</blockquote><div>
<br>Very strange ... I've now installed the latest snapshot, and the problem persists. This time on a Gentoo installation with Qt 4.2.2. Inspecting the generated Python bindings, sipQtGuiQGraphicsScene.cpp, it seems to me there is a bug in meth_QGraphicsScene_drawItems. Argument 3, an array of QGraphicsItem*, is actually treated as a return value from the corresponding C++ function and thus uninitialized before being passed to Qt. As such I wonder how come it doesn't crash on your machine, maybe the memory error is not detected?
<br><br>If you print out the arguments to drawItems in Python you'll find that instead of a list of QGraphicItems you'll receive an int instead (the number of items).<br><br>Arve<br></div><br></div>