Russian Qt Forum

т.е. использование sender() в этом случае не подходит по многим причинам ( в том числе недоступности объектов в слоте ).

известно что при обработке сигнала, передача управления происходит в порядке подключения сигнала к слоту (по номерам)

The QSignalMapper class bundles signals from identifiable senders.

This class collects a set of parameterless signals, and re-emits them with integer, string or widget parameters corresponding to the object that sent the signal.

The class supports the mapping of particular strings or integers with particular objects using setMapping(). The objects' signals can then be connected to the map() slot which will emit the mapped() signal with the string or integer associated with the original signalling object. Mappings can be removed later using removeMappings().

Example: Suppose we want to create a custom widget that contains a group of buttons (like a tool palette). One approach is to connect each button's clicked() signal to its own custom slot; but in this example we want to connect all the buttons to a single slot and parameterize the slot by the button that was clicked.

Here's the definition of a simple custom widget that has a single signal, clicked(), which is emitted with the text of the button that was clicked:

основная идея была передать параметр, с которым вызывать слот по происшествии сигнала. Действительно, если знать от кого пришел сигнал (кнопка, action), то многое решается доп

void SomeClass::someSlot()
{
    QObject *obj = sender();
    if (!obj) return;

    if (qobject_cast<QAction *>(obj)) {
        <do_something with QAction> 
        return;
    }

    if (qobject_cast<QPushButton *>(obj)) {
        <do_something with QPushButton> 
        return;
    }
}

bool QObject::inherits ( const char * className ) const
const char * QMetaObject::className () const