A list for storing member functions/slots?

[Akiva]

Ha, you are right about a few things there, especially about having to add all all these to a list partially defeating the purpose of such a loop. Despite this, we have our reasons to do this. One such reason is to easily change the signal and perhaps add some more later. For what its worth, here is our: project https://launchpad.net/dominion.linux

So you were quite on target with the board game suspicion.

Anyway, I will look at the Signal Mapper for sure; There is always so much to learn!

[ChrisW67]

Since each QToolButton is a QObject you already have a generic way to get/set any declared property of the button without knowing the specific class of the button: QObject::property() and QObject::setProperty(). You can access information on available properties through the QMetaObject of the QToolButton.

If all the tool buttons belong to a single parent object then you can access them using the child list of the parent using QObject::findChildren() without necessarily maintanng a separate list.

Have a think about how these functions might be useful to you.

[anda_skoa]

Good suggestion Chris.

Additional to that all buttons could connect to the same slot, QObject::sender() could be used to retrieve the button and then QObject:roperty() could be used to extract the respective parameters.

Of, if all buttons have the same types of parameters but just different values, create a QToolButton subclass that has methods for those and cast QObject::sender() to that class and call the getters directly.

Another option would be to have separate receiver objects, one for each button. Each such instance would get its individual parameters upon construction, thus not needing any in the slot.

e.g.

class ButtonReceiver : public QObject
{
  Q_OBJECT
public:
  ButtonReceiver( /* parameter */, QObject *parent = 0);
 
public slots:
  void onButtonClicked();
};

class ButtonReceiver : public QObject
{
  Q_OBJECT
public:
  ButtonReceiver( /* parameter */, QObject *parent = 0);

public slots:
  void onButtonClicked();
};

To copy to clipboard, switch view to plain text mode 

QList<ButtonReceiver*> receiverList;

QList<ButtonReceiver*> receiverList;

To copy to clipboard, switch view to plain text mode 

for (int i = 0; i < buttonList; ++i) {
  connect(buttonList[i], SIGNAL(clicked()), receiverList[i], SLOT(onButtonClicked()));
}

for (int i = 0; i < buttonList; ++i) {
  connect(buttonList[i], SIGNAL(clicked()), receiverList[i], SLOT(onButtonClicked()));
}

To copy to clipboard, switch view to plain text mode 

Cheers,
_

[wysota]

I have taken a look at the code in the repository mentioned by OP. The code there contains a couple hundred of practically identical slots generated by some external python tool.