Wow, that's an oldie. I think eventually solved my problem by using deleteLater() to explicitly delete widgets, instead of just 'myObj =None' or 'del myObj'.
If I remember right, there were two issues:
1) It turned out that in some cases I was deleting an object while processing a signal involving the object or a child of the object (probably a bad idea).
2) There still seemed to be some inexplicable cases where Qt's bookkeeping was getting messed up.
Using deleteLater() seemed to fix everything. I suggest using it if you're deleting widgets, especially inside any event or signal handling.
Andy Anderson
MSC.Software Corporation
[EMAIL PROTECTED] wrote on 03/17/2006 11:02:58 AM:
> I checked all the __init__ functions, but I hadn't missed anything as
> you mentioned. However, I catched another traceback which is smaller
> and complete.
>
> I searched the previous mails in the archieve and found these
>
> http://mats.imk.fraunhofer.de/pipermail/pykde/2003-November/006529.html
> http://mats.imk.fraunhofer.de/pipermail/pykde/2003-November/006508.html
>
> They had also faced the same problem like mine, but there seems to be
> no solution.
>
> Mike
_______________________________________________ PyKDE mailing list [email protected] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
