Extending QAction by emitting additional Signals: Difference between revisions
(Code Review) |
Waldyrious (talk | contribs) Tag: Undo |
||
(3 intermediate revisions by 2 users not shown) | |||
Line 96: | Line 96: | ||
<code> | <code> | ||
CheckableAction | CheckableAction *myAction = new CheckableAction( this ); | ||
myAction->setText( tr("Action TEXT") ); | |||
myAction->setIcon( QIcon(":/actions/img/myaction.png") ); | |||
myAction->setStatusTip( tr("Check/Uncheck the action") ); | |||
myAction->setCheckable( true ); | |||
connect( myAction, SIGNAL(actionChecked()), | |||
this, SLOT(slotActionUncheked()) | |||
); | |||
connect( myAction, SIGNAL(actionUnchecked()), | |||
this, SLOT(slotActionCheked()) | |||
); | |||
</code> | </code> |
Latest revision as of 23:35, 22 November 2022
Introduction
QActions can be set up to be checkable, that means that it will toggle its status between a checked and unchecked state. This is displayed, for instance, as a QPushButton that remains repressed when clicked a first time. The problem with QAction is that it emits a single signal, triggered(bool), with the actual status of the action (if checked or not). This requires your slot to manually check the boolean flag to perform a specific behavior depending on the checked status. If you want your action to perform two different tasks without having to check the checked status of the action you can subclass the action implementing a couple of signals to emit events depending on the action internal status.
This can become very handy when you have got a set of actions that must be perform a different behavior when checked but must do all the same task when unchecked.
Source Code
The source code is really simple. Here there is the header file:
#ifndef CHECKABLEACTION_H
#define CHECKABLEACTION_H
#include <QAction>
#include <QDebug>
/*!
* This class represents an action that will emit
* distinct signals depending on the check of the
* action itself.
*/
class CheckableAction : public QAction
{
Q_OBJECT
public:
explicit CheckableAction(QObject *parent = 0);
signals:
/*!
* This signal is emitted each time the action is
* checked.
*/
void actionChecked();
/*!
* This signal is emitted each time the action is
* unchecked.
*/
void actionUnchecked();
public slots:
private slots:
/*!
* This slot is used to forward (i.e., emit) a triggered
* event depending on the status of the action (i.e., if it
* has been checked or not).
* checked true if the action has been checked, false
* otherwise
*/
void slotForwardCheckSignal( bool checked );
};
#endif // CHECKABLEACTION_H
and here the implementation of the class
#include "checkableaction.h"
CheckableAction::CheckableAction(QObject *parent) :
QAction(parent)
{
// auto connect the triggered event to the slot for
// forwarding the check status
connect( this, SIGNAL(triggered(bool)),
this, SLOT(slotForwardCheckSignal(bool))
);
}
void CheckableAction::slotForwardCheckSignal(bool checked)
{
qDebug() << "Action checked status " << checked;
// check the status of the action
if( ! isCheckable() ) {
// the action cannot be checked, simply emit
// a triggered event
triggered();
} else
if( isChecked() ) {
// the action is checked
emit actionChecked();
}
else {
// the action is unchecked
emit actionUnchecked();
}
}
Usage Example
The action can be used in the way a QAction is, for instance:
CheckableAction *myAction = new CheckableAction( this );
myAction->setText( tr("Action TEXT") );
myAction->setIcon( QIcon(":/actions/img/myaction.png") );
myAction->setStatusTip( tr("Check/Uncheck the action") );
myAction->setCheckable( true );
connect( myAction, SIGNAL(actionChecked()),
this, SLOT(slotActionUncheked())
);
connect( myAction, SIGNAL(actionUnchecked()),
this, SLOT(slotActionCheked())
);