Signature not normalized warning

[Kaluss]

Hi,
I got following annoying problem:

I have following warning in my code:
Signature is not normalized. Use locationCodeChanged(QString) instead of locationCodeChanged( QString ) [clazy-connect-not-normalized]

I found this:
https://forum.qt.io/topic/18651/understanding-signature-normalization-for-signals-and-slots
but it doesn't help.

My signal takes QString and slot takes const QString&.

How should it look like to get rid of it?

[Pl45m4]

@Kaluss said in Signature not normalized warning:

Use locationCodeChanged(QString) instead of locationCodeChanged( QString )

Do this.
Normalization also removes spaces.
If you write locationCodeChanged(QString) the warning should be gone.

[Christian Ehrlicher]

Or even better - use the new signal slot syntax.

[Kaluss]

@Christian-Ehrlicher ok, I will use new syntax, but regarding old one:
removed all spaces as @Pl45m4 suggested, but it doesn't help at all:

Is it even possible to get rid of this warning in old syntax?

[JonB]

@Kaluss said in Signature not normalized warning:

My signal takes QString and slot takes const QString&.

Then why does your SLOT() not take const QString&?

I would save file, exit, re-enter, and show exact warning being shown, not chopped off as per your last....

[Kaluss]

@JonB it's not taking const QString& according to this:
https://forum.qt.io/topic/18651/understanding-signature-normalization-for-signals-and-slots

[JonB]

@Kaluss
If you say so, since you won't show the full message against the changed signature I don't know.

Whatever it's another reason not to waste time on a syntax which was replaced for the better a decade ago.

[SGaist]

@Kaluss said in Signature not normalized warning:

My signal takes QString and slot takes const QString&.

Out of curiosity, why not use a ˋconst QString &` as well for your signal ? There no reason to force a copy when it's not needed.