Hi all, I was taking a look at bug 29498[0] and the explanation is pretty clear on what's happening: disconnect admits char * signal = 0 as a parameter (which means all signals) but then forwards that parameter to other calls that apparently do not commit to support 0 as a possible value.
I can take care of this bug but the question is how do we prefer to fix it: should we multiplex at QObject::disconnect level or start looking around to support signal = 0 in all other places? David E. Narváez [0] https://bugreports.qt-project.org/browse/QTBUG-29498 _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
