Can't connect SIGNAL to SLOT in same classe and also two differents classes

[J.Hilk]

@jawad_soft said in Can't connect SIGNAL to SLOT in same classe and also two differents classes:

connect(socket, SIGNAL(ack_gui(QString)), this, SLOT(ackRead(QString)));

this
connect(this, SIGNAL(ack_gui(QString)), this, SLOT(ackRead(QString)));

or (better)
connect(this, &UDPServer::ack_gui, this, &UDPServer::ackRead);

[JonB]

@jawad_soft said in Can't connect SIGNAL to SLOT in same classe and also two differents classes:

I also tried the new connect syntax in QT5 but it didn't work.

As others have said: please change over to the new-style syntax always! No need to ever use SIGNAL/SLOT() macros. If the new-style "doesn't work", at least it's giving you compile-time help on why not, which you must address!

[J.Hilk]

@JonB said in Can't connect SIGNAL to SLOT in same classe and also two differents classes:

No need to ever use SIGNAL/SLOT() macros

I have at least 1 use case where the use of old macros is essential 😉
Fringe case, but it exists

[JonB]

@J-Hilk
Of course I respect your comment/case. However, do you think this is good advice for the OP here? Or do you think he would be better advised not using this as an excuse to stay with old-style but would be better using new-style for all his cases?

[J.Hilk]

@JonB Fair enough point I'm only objecting to the generalization, there's a reason why you don't get a whole bunch of deprecated warning when you use the old syntax.

Even though you should, in my opinion at least.

[jawad_soft]

@J-Hilk @raven-worx ! Thanks for reply, effectively it works better, I don't see the connection failure message, but what about the arguments of signal and slot ? :D I will even take the opportunity to use the new syntax.

my goal was to connect the signal ack_gui that i created in this class with the slot of my classe mainwindows class, should i integrate it this way :

mainwindows .h :

#ifndef MAINWINDOW_H
#define MAINWINDOW_H

#include <QMainWindow>
#include <QPushButton>
#include <QApplication>
#include <QDesktopWidget>
#include <QObject>
#include <QWidget>
#include <QLabel>
#include <QTextStream>
#include <QTimer>
#include <QLoggingCategory>
#include <QGraphicsView>
#include <QGraphicsRectItem>
#include <QVariantAnimation>
#include <QGraphicsScene>
#include <QGraphicsProxyWidget>

#include "udpserver.h"


namespace Ui {
class MainWindow;
}

class MainWindow : public QMainWindow
{
    Q_OBJECT

private:

    QColor menuButtonColor;

    Ui::MainWindow *m_ui;
    QPushButton *m_Button;

    void init();

private slots:
    void onLaunchButton(QString ackMsg);
    void onLaunchButton();


protected:
    bool event(QEvent *event) override;

public:
    explicit MainWindow(QWidget *parent = nullptr);
    ~MainWindow() override;


public slots:
    void update_data();
};

#endif // MAINWINDOW_H

mainwindows .cpp :

#include "mainwindow.h"
#include "ui_mainwindow.h"
#include <QFile>
#include <QTextStream>


MainWindow::MainWindow(QWidget *parent) :
    QMainWindow(parent, Qt::FramelessWindowHint),
    m_ui(new Ui::MainWindow)
{
        UDPServer client;
  
       QObject::connect(m_Button, SIGNAL(clicked()),this, SLOT(onLaunchButton()));
       connect(client.getSocket(), &UDPServer::ack_gui, this, &MainWindow::onLaunchButton(QString));
}

With function client.getSocket() i will get socket private attribut of UDPServer , I feel like I'm going to make the same error again how I refer to the UDP socket class from the class MainWindow ?

Thank you again for your help

[J.Hilk]

@jawad_soft said in Can't connect SIGNAL to SLOT in same classe and also two differents classes:

With function client.getSocket() i will get socket private attribut of UDPServer , I feel like I'm going to make the same error again how I refer to the UDP socket class from the class MainWindow ?

correct, UDPServer::ack_gui is part of the UDPServer class and your instance of that class is (apparently) simply client therefore:

connect(client, &UDPServer::ack_gui, this, &MainWindow::onLaunchButton);

---

Edit:
but you have to drop the QString argument, the new syntax does not require / allow that

[jawad_soft]

@J-Hilk ! Ok , i Suppose with new syntaxe you can't have slots with same name and differents arguments haha !!
I got error when i implement the line :

connect(client, &UDPServer::ack_gui, this, &MainWindow::onLaunchButton);

Errore =>

no matching member function for call to 'connect'

I try to add this :

QObject::connect(client, &UDPServer::ack_gui, this, &MainWindow::onLaunchButton);

But nothing change !?

[J.Hilk]

@jawad_soft
ok we can fix that because client is stack allocated not heap and a local variable,

BUT

thats only fix of the bug here's an underlying bigger issue, client should probably be a class member, because it will be destroyed, as soon as the constructor exits!

The "Fix"

connect(&client, &UDPServer::ack_gui, this, &MainWindow::onLaunchButton);

i Suppose with new syntaxe you can't have slots with same name and differents arguments haha

of course you can thats what qOverload is for :D
https://doc.qt.io/qt-5/qtglobal.html#qOverload

[jawad_soft]

@J-Hilk Great explanation ! I solved my problem and at the same time I learned more things.