QCheckBox: is it really not possible to differentiate between user-induced changes to state and those made programmatically? If so, should it be considered an inconsistency?

Question

Do I miss something or there is really no (ready / built-in) way to programmatically change the state of a QCheckBox without emitting the "void stateChanged ( int state )" signal?

The above-mentioned signal is emitted regardless of whether "void setCheckState ( Qt::CheckState state )" was called or the user changed the state via the ui, and there is no "stateEdited" signal like with the QLineEdit.

So, if there is no ready way to differentiate between programmatic and user-induced changes to the state of the QCheckBox, and the only options are subclassing / adding the "stateEdited" signal or fiddling with "void QObject::blockSignals( bool block )", why does this have to be so, i.e., is it an (some sort of) inconsistency (in Qt)?

Thanks in advance, and forgive my English.

Answer 1

If you want to

programatically change the state of a QCheckBox

use setCheckState method.

P.S. I do not understand what does it mean

change the state of a QCheckBox ... emitting a "void stateChanged ( int state )" signal

Probably you should read Signals and Slots topic more carefully.

Answer 2

If you only need to be informed of user input, listen to

QAbstractButton::clicked( bool checked );

Otherwise connect to

QAbstractButton::toggled( bool checked );

or

QCheckBox::stateChanged( int state);