When I ran into this, it has almost always been because of method
parameters initialized with default values in the constructor of some
PySide class. Let’s say class A gets instanced twice. If instance X is
garbage collected for whatever reason, when instance Y tries to use Y.b
it’ll complain
Qt (C++) usually honors the parent-child relationship, so it won't
automatically delete a widget unless its parent is being deleted. And if it
doesn't have a parent, it shouldn't be automatically deleted by reference
count unless it is wrapped in a smart pointer. Or maybe you have looked up
a
Hi Marcus, thanks for the reply.
You see, that is what i want to avoid at all costs. I dont want this thread
conversation to evolve following a concrete, specific use case, but rather
try to aim at "the bigger" picture. There are may examples of where and how
this C++ already deleted error
It would certainly help if you could provide an example of something that
causes the error, or at the very least a stacktrace of the error.
On Saturday 23 March 2024 at 18:04:59 UTC rainonthescare...@gmail.com wrote:
> Hi,
> i ve been working for quite some time now and occasionally bumped into
Hi,
i ve been working for quite some time now and occasionally bumped into this
C++ "unfamous" error. Normally, when found occasionally, ive been able to
fix it by using the widget's "self.findChild"/"self.findChildren" which i
believe keeps the C++ reference count of the object's pointer alive.
