slot will be called multi-times if connect() multi-times, is there any way to check this error?

opengpu2

@SeeLook what should i do if i set the last argument Qt::QueuedConnection...

SeeLook

This post is deleted!

SeeLook

@opengpu2 Do You have some reason for that?
Here is doc of connection types:
http://doc.qt.io/qt-5.5/qt.html#ConnectionType-enum

Jakob

@opengpu2 You can combine options: simply use Qt::QueuedConnection | Qt::UniqueConnection as last argument to the connect call

SGaist

Hi,

Connect doesn't overwrite anything, it just creates a new connection unless you use Qt:UniqueConnection like our fellows suggested.

However that's an option that's rarely used, what is your use case ?

opengpu2

@SeeLook yep, cross thread use QueuedConnection

opengpu2

@Jakob so if i set Qt::UniqueConnection, that is equal to Qt::QueuedConnection | Qt::UniqueConnection. right?

opengpu2

@SGaist i wonder why Qt allow the same connect to be created multi-times... i wrongly wrote some connect in func except Constructor&Init(). and when that func is called multi-times, then each emit will cause multi-time slot...
i think Qt:UniqueConnection is set by default will be more safe.
can i write a custom macro to replace all connect and let them use Qt:UniqueConnection

opengpu2

@Jakob i directly set the last param as Qt::QueuedConnection | Qt::UniqueConnection, but there is error canno convert from 'int' to 'Qt::ConnectionType'.
so i have to write like this? (Qt::ConnectionType)(Qt::QueuedConnection | Qt::UniqueConnection)

SGaist

While there are valid use cases, most of the time creating the exact same connection several times is a design/coding error so making UniqueConnection the default would just hide it and thus open the path to hard to debug behavior/bugs.

opengpu2

@SGaist ok thank you