<br><font size=2 face="sans-serif">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'.</font>
<br>
<br><font size=2 face="sans-serif">If I remember right, there were two
issues:</font>
<br>
<br><font size=2 face="sans-serif">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).</font>
<br><font size=2 face="sans-serif">2) There still seemed to be some inexplicable
cases where Qt's bookkeeping was getting messed up.</font>
<br>
<br><font size=2 face="sans-serif">Using deleteLater() seemed to fix everything.
I suggest using it if you're deleting widgets, especially inside any event
or signal handling.</font>
<br><font size=2 face="sans-serif"><br>
Andy Anderson<br>
MSC.Software Corporation<br>
</font>
<br>
<br><font size=2><tt>pykde-bounces@mats.imk.fraunhofer.de wrote on 03/17/2006
11:02:58 AM:<br>
<br>
> I checked all the __init__ functions, but I hadn't missed anything
as<br>
> you mentioned. However, I catched another traceback which is smaller<br>
> and complete.<br>
> <br>
> I searched the previous mails in the archieve and found these<br>
> <br>
> http://mats.imk.fraunhofer.de/pipermail/pykde/2003-November/006529.html<br>
> http://mats.imk.fraunhofer.de/pipermail/pykde/2003-November/006508.html<br>
> <br>
> They had also faced the same problem like mine, but there seems to
be<br>
> no solution.<br>
> <br>
> Mike<br>
</tt></font>