Presumably you can do the same against QLineEdit::textEdited. Note that there is a potential little wriggle. If you're not careful, you change the model, it then changes the widget, and then that re-raises the "changed" signal and you get stuck forever. My slot reads the current value from the model and exits if the value passed to the slot is the same as that retrieved from the model. I also use Qt::QueuedConnection to prevent the slot causing changes while still within the original signal call, which was a problem. These may be because I am using QSpinBoxes, may not apply when using QLineEdit::textEdited (which is a different signal from QLineEdit::textChanged which will be emitted when you change the value in the model programmatically and it reflects back to the widget).