On 4/28/06, <b class="gmail_sendername">Phil Thompson</b> <<a href="mailto:phil@riverbankcomputing.co.uk">phil@riverbankcomputing.co.uk</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>QCanvasSprite does not take responsibility for calling the QPixmapArray dtor,<br>ie. it doesn't take ownership of the QPixmapArray instance. Therefore, when<br>the latter goes out of scope it is garbage collected (unless there is another
<br>reference to it). Your solution is the conventional way of handling it.<br><br>Python isn't C++.</blockquote><div><br>
I gathered that :-) Ok, but how about QCanvas? Apparently, the canvas *does* take ownership of <br>
any item put on it, even though its situation is similar to that of QCanvasSprite. Or does it just seem<br>
that way, and am I taking horrible risks with the example in my previous post which for some odd <br>
reason haven't blown up in my face yet?<br>
</div><br>
</div>-- <br>Alex Borghgraef