SDK Qt Creator autocomplete removes const from SIGNAL and SLOT signatures

Have you got example source code with which this can be reproduced?

I believe your example above should get autocompleted to SIGNAL(foo(QString)). The const or & should not be part of the autocompletion or the code you write. It seems to work as I described for me, but perhaps you have some code segment that is triggering an error in autocompletion?

Here's a bugfix for such an error: https://github.com/smokku/pebble/commit/e47e1202518ab72658ab8d659b081b71fdd8609f#diff-90291d1305a30fca5e4a577b83910a7eR28

The issue is that QDBusConnectionInterface emits void serviceUnregistered(const QString &) but autocompleted signature is SIGNAL(serviceRegistered(QString&)), which gets compiled OK (as SIGNAL macro generates plain string) but errors on runtime, with "no such signal" error.

Yeah, I can get that funky autocompletion with the serviceUnregistered signal.

It might have something to do with the way the signal is declared in qt's own header file (qdbusconnectioninterface.h):

void serviceUnregistered(const QString &service);

If I change that to have a space between the "&" and "service", then the autocompletion will insert just serviceRegistered(QString) there without the const and &, which is fine.

So it looks like a bug in Qt Creator. Will have to check if it's still there in Qt Creator 3.x.

Unfortunately it does not work any better in Qt Creator 3. By the way, this article and some Qt's own documentation prefers normalised signatures over const references:

http://marcmutz.wordpress.com/effective-qt/prefer-to-use-normalised-signalslot-signatures/