On Fri, Mar 8, 2013 at 1:48 AM, Thiago Macieira
wrote:
> Effectively, disconnectNotify will get a null pointer (Qt4) or an invalid
> QMetaMethod (Qt5) to mean that all signals are being disconnected. The
> receiver needs to deal with it.
So wildcard arguments are detected at
QDBusAbstractInterfac
On sexta-feira, 8 de março de 2013 07.29.16, Olivier Goffart wrote:
> I think it is best to handle properly the cases in each reimplementation of
> disconnectNotify.
Effectively, disconnectNotify will get a null pointer (Qt4) or an invalid
QMetaMethod (Qt5) to mean that all signals are being disco
On Thursday 07 March 2013 23:58:36 David Narvaez wrote:
> 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
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 t
