Correct syntax to register object reference using qRegisterMetaType?

[SPlatten]

@kshegunov , I am using const QJsonObject& for my signal arguments, these are working, the only thing that is displayed in the Application Output is the message I've raised. I'm not experience any other problems, crashes or bugs.

[JonB]

@SPlatten
The signal argument type is "OK", insofar as it would work OK with non-cross-thread direct connection connect()s. But the problem is that you are trying to use it when you need a queued connection. That is why you get the error message on the QObject::connect statement.

[SPlatten]

@JonB , thank you, I'll take a look.

[SGaist]

@SPlatten said in Correct syntax to register object reference using qRegisterMetaType?:

@kshegunov , I am using const QJsonObject& for my signal arguments, these are working, the only thing that is displayed in the Application Output is the message I've raised. I'm not experience any other problems, crashes or bugs.

For the slots as well ?

[SPlatten]

@SGaist Of course.

[SPlatten]

Ok, I've now got rid of the warning, by going through all the QObject::connect calls and only using Qt::DirectionConnection where the signal and slot pointers are the same.

[JonB]

@SPlatten
A lot of your questions are about threads. Are your connect()s' senders/receivers never in separate threads?

[SPlatten]

@JonB , not for the ones where I've used Qt::DirectConnection

[Christian Ehrlicher]

@SPlatten said in Correct syntax to register object reference using qRegisterMetaType?:

not for the ones where I've used Qt::DirectConnection

Then it's useless since then Qt::AutoConnection evaluates to Qt::DirectConnection. Specifying a connection type is not needed in most of the cases.

[SPlatten]

@Christian-Ehrlicher , Well that's the only change I'm implemented and now there is no message, so perhaps this is something that needs looking at?

[SGaist]

@SPlatten said in Correct syntax to register object reference using qRegisterMetaType?:

@Christian-Ehrlicher , Well that's the only change I'm implemented and now there is no message, so perhaps this is something that needs looking at?

For that a minimal compilable example would be needed.

[Christian Ehrlicher]

@SPlatten said in Correct syntax to register object reference using qRegisterMetaType?:

so perhaps this is something that needs looking at?

This means that there is a thread context switch somewhere even you tell us it isn't.

[kshegunov]

@SPlatten said in Correct syntax to register object reference using qRegisterMetaType?:

@Christian-Ehrlicher , Well that's the only change I'm implemented and now there is no message, so perhaps this is something that needs looking at?

Run with QT_FATAL_WARNINGS=1 as an environment variable and extract the stack trace, then you will have leveraged your debugger to show you exactly where you're passing a reference between threads.

[SPlatten]

@kshegunov said in Correct syntax to register object reference using qRegisterMetaType?:

QT_FATAL_WARNINGS=1

I've opened both .pro files and added that line, then cleaned and rebuilt, the applications have been running for several minutes, nothing to report, no issues.

[SGaist]

It's an environnement variable, not a define.

You have to set it in the Run tab of the Project panel.

[SPlatten]

@SGaist , Yes, just googled it and then added as environment variable:

export QT_FATAL_WARNINGS=1

Then restarted, same, not seeing anything additional.

[SGaist]

Restarted what ?
How are you currently running your application ?

[SPlatten]

@SGaist , I launch the processes with Qt Creator in debug mode, using two separate instances of Qt Creator.

[SGaist]

Did you check the environment variables in the Run part of the Project Panel to ensure it's properly set ?

[SPlatten]

@SGaist , I checked in a terminal, I don't know how or where to "Run part of the Project Panel" ?