[Development] Fixing connecting to private signals

[Olivier Goffart]

On Friday 13 July 2012 09:57:49 Olivier Goffart wrote:
> On Friday 13 July 2012 09:30:44 Thiago Macieira wrote:
> > On sexta-feira, 13 de julho de 2012 08.33.42, Girish Ramakrishnan wrote:
> > > Is this really important given that we are in feature freeze? Changes
> > > to moc, however small, is not advisable at all.
> 
> This is why we brought the subject on the mailing list.
> 
> > As I wrote in the change, this breaks if there are overloads to the
> > signal:
> > 
> > signals:
> >     void somethingChanged();
> >     void somethingChanged(int, QPrivateSignal);
> > 
> > You can't connect to the private signal because the type QPrivateSignal is
> > private.
> 
> Yes that's right.
> But signal overload should be avoided.

Maybe moc should even warn if the signal overload another function.

-- 
Olivier

Woboq - Qt services and support - http://woboq.com