QCanvasSprite does not take responsibility for calling the QPixmapArray dtor,
ie. it doesn't take ownership of the QPixmapArray instance. Therefore, when
the latter goes out of scope it is garbage collected (unless there is another
reference to it). Your solution is the conventional way of handling it.
Python isn't C++.
I gathered that :-) Ok, but how about QCanvas? Apparently, the canvas *does* take ownership of
any item put on it, even though its situation is similar to that of QCanvasSprite. Or does it just seem
that way, and am I taking horrible risks with the example in my previous post which for some odd
reason haven't blown up in my face yet?
Alex Borghgraef
_______________________________________________ PyKDE mailing list [email protected] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
