QT connect versus socket connect...
-
QT connect versus socket connect
I am using ancient Bluetooth C code example and painted myself into a corner...
How do I instruct the compiler to use "socket connect" AND not "QT connect " ?
status = connect(s, (struct sockaddr *)&addr, sizeof(addr));
-
It's a function in global scope, so you can explicitly state that scope to differentiate from the QObject member function:
status = ::connect(s, (struct sockaddr *)&addr, sizeof(addr));
-
... and the groundhog says hello every
dayyear: https://forum.qt.io/topic/121943/whoops-complier-see-qt-connect-is-a-dupe