A list for storing member functions/slots?

[Akiva]

Thank you for your honest reply.

You are right to point out that my terminology could be more concise, and I greatly appreciate it, despite any apparent frustration on my part. It forces me to elevate my venacular, and become a better programmer.

By "Basic Properties" I merely meant to do the same thing as what QtDesigner's "Property Editor" does. For example, the property editor will allow you to set the maximum and minimum sizes of most QWidgets, as well as some other things. I am not sure what other term to use besides "Properties".
By instructions, I merely meant to reference any various signals or slots pertaining to the QToolButton, and in my case, the task of connecting my signals to my slots. My use of the term "Instructions" must clearly be wrong, so I apologize.

I'll try to be even more concise with my example. All I want to accomplish is this:

ListOfSlots->append(NameOfSomeSlot());
ListOfButtons->append(NameOfSomeButton)
 
for( int i = 0; i < ListOfSlots.size(); i++ )
{
connect(ListOfButtons->at(i),SIGNAL(clicked()), this, SLOT(ListOfSlots->at(i)()));
}

ListOfSlots->append(NameOfSomeSlot());
ListOfButtons->append(NameOfSomeButton)

for( int i = 0; i < ListOfSlots.size(); i++ )
{
connect(ListOfButtons->at(i),SIGNAL(clicked()), this, SLOT(ListOfSlots->at(i)()));
}

To copy to clipboard, switch view to plain text mode 

I really appreciate your patience in all of this.

[wysota]

To me what you want to accomplish will not make your code shorter as you still have to add all those slot names to the list, but here you go:

QList<const char*> slotList;
slotList << SLOT(slot1());
slotList << SLOT(slot2());
// ...
 
for(int i=0; i< listOfButtons.size();++i) {
  connect(listOfButtons->at(i), SIGNAL(clicked()), this, slotList.at(i));
}

QList<const char*> slotList;
slotList << SLOT(slot1());
slotList << SLOT(slot2());
// ...

for(int i=0; i< listOfButtons.size();++i) {
  connect(listOfButtons->at(i), SIGNAL(clicked()), this, slotList.at(i));
}

To copy to clipboard, switch view to plain text mode 

Having said that I have to admit it all makes little sense to me. I'm assuming you are programming some kind of game (possibly a board game?) and you are using all those buttons for some kind of fields or pieces. In my opinion a much better approach would be to use Graphics View or at least to use a QSignalMapper and connect all your buttons to a single slot keyed by the button id.

[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.