[prev in list] [next in list] [prev in thread] [next in thread]
List: pykde
Subject: Re: [PyQt] Slots being called on deleted QObjects
From: Jeremy Sanders <jeremy () jeremysanders ! net>
Date: 2014-04-08 8:31:15
Message-ID: li0c4e$6u3$1 () ger ! gmane ! org
[Download RAW message or body]
Phil Thompson wrote:
> What would the default be? Reinstating the check by default would be
> another incompatible change (though documented this time) but would be
> fixing a 2 year old regression, and would be the "right thing" for the
> vast majority of cases.
>
> Thoughts?
In my opinion reverting it would be the right thing for most people.
Personally, I've never wanted to get a signal on an object with a destroyed
QObject, but perhaps there's a use case somewhere (besides destroyed?).
Is there a merit to special-casing destroyed() and/or adding a flag (to
connect maybe) which will always deliver the signal to the object?
Jeremy
_______________________________________________
PyQt mailing list PyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic