Can I "connect" using QAction as sender ?

[Anonymous_Banned275]

EDIT
I got the answer here

https://forum.qt.io/topic/131708/multiple-qaction-and-using-sender-to-get-which-got-selected/2

Very basic question, and if the answer is no , can you suggest alternative to "connect" using QAction ?

The attached TEST C++ code works with sender QMenu and gets me ton of error messages when the sender is QAction,

                        connect(subMenu[index_sub] , &QMenu::triggered, this ,
                                [=]() { this->processAction(index_sub,index) ;});

                        // connect to main submenu
connect(TEMP_[index] ,  &QMenu::triggered, this ,[=]() { this->processAction(index_sub,index) ;});

[Pl45m4]

@AnneRanch

If the signal is not there in QAction, how would you be able to use it?! Of course it does't work, if you use random signals and try to use them with other classes...

@AnneRanch said in Can I "connect" using QAction as sender ?:

connect(TEMP_[index] , &QMenu::triggered,

And if TEMP_[index] is a QAction, you need to change it to &QAction::triggered

[Anonymous_Banned275]

@Pl45m4 Thanks, just found my error.

[Axel Spoerl]

@AnneRanch

@Chris-Kawa explained here, how actions are added to a menu.

If I remember your code correctly from previous posts, TEMP_is an array of QMenu.
So the connect statement connects to a menu, which works only with signals of QMenuor one of its base classes. QAction isn't such a base class of QMenu, which is the reason for your compiler errors.

It's not possible to suggest a working alternative, because we don't know where you store the pointer to the QActionreturned by addAction("yourText").
Let's assume it is stored in QAction *tempAction.
In that case the following would work:

connect(tempAction, &QAction::triggered, this, [=]() {this->processAction(index_sub, index); });