On Feb 7, 2008 5:54 PM, Emmanuele Bassi <[EMAIL PROTECTED]> wrote: > my point, if it wasn't clear - and by now I kinda guessed it really > wasn't - is that you can avoid leaking by simply *not* doing what you > are doing, as there are ways to reimplement the same functionality in a > safe way.
Yep, you are of course correct. What I've now learnt is that if I implement widgets in python inheriting from clutter classes: - I should not use any of the clutter.effect_*() functions for Actors implemented in python - I should not store clutter objects (or any other gobject) to member variables of python based Actor *if* the object in question holds reference back to the Actor breaking these rules causes noncollectable objects. This still doesn't sound right to me... There must be some general knowledge about gobject+python which I've just missed... ;-) Anyway, thanks for your help and for the great library! -- Tero -- To unsubscribe send a mail to [EMAIL PROTECTED]
