On Monday 05 August 2013 22:29:20 Jan Kundrát wrote: > > >> you mean to disconnect(job, 0, this, 0)? > > > > I think this is to protect against stop() emitting any > > signals. Probably easier to call job->disconnect(); > > Or avoiding sigals in stop(). > > I was thinking about another valid use case, something > watching for object deletion. IMHO it's concievable to have a > monitor of all pending jobs which listens for > QObject::destroyed(QObject*). This disconnect will suddenly > break this use case. > > I was worried that this might even break QPointer, but it > turns out that it's using a completely different mechanism > than signals/slots (QObject::addGuard). I learned yet another > new thing today -- cool. Anyway, I'm not sure whether this is > usable for the monitor use case. > > Why is there the need to mute the signals anyway? >
As Kevin wrote, protection against emitting signals. -- Pali Rohár pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
