Thanks. I need an accurate list of children in response to a child's destroyed signal, so is the best way to do this, then, to have Parent maintain its own list of Children, rather than using findChildren(), and use the destroyed(QObject*) version of the signal to explicitly remove the Child from the Parents list?
J On Mon, Mar 19, 2012 at 11:52 AM, Thiago Macieira <[email protected] > wrote: > On segunda-feira, 19 de março de 2012 11.34.02, Jason Cipriani wrote: > > I am new to Qt. I have two QObject-derived classes, Parent and Child. > > Child's parent is a Parent. When I attach a slot in Parent to Child's > > destroyed() signal, I see that Parent's findChildren() does not include > the > > Child that was destroyed. This is what I want. Calling findChildren() in > a > > destroyed() handler, and assuming the child won't be in the list, is > safe, > > right? > > Don't assume that. > > The order in which the signal and the child deletion is run could change > in a > different version. > > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel Open Source Technology Center > Intel Sweden AB - Registration Number: 556189-6027 > Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden > > _______________________________________________ > Interest mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/interest > >
_______________________________________________ Interest mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/interest
