Trolltech Home | Qt4-preview-feedback Home | Recent Threads | All Threads | Author | Date
All threads index page 1

Qt4-preview-feedback Archive, May 2007
inconsistency between QSpinBox and the other classes typically used in forms, qt-4.3.0-20070505

• Subject: inconsistency between QSpinBox and the other classes typically used in forms, qt-4.3.0-20070505
• From: Nico Kruber <Nico.Laus.2001@xxxxxx>
• Date: Tue, 8 May 2007 11:08:18 +0100
• Delivered-to: qt4-preview-feedback@trolltech.com
• List-help: <mailto:qt4-preview-feedback-request@trolltech.com?subject=help>
• List-post: <mailto:qt4-preview-feedback@trolltech.com>
• List-subscribe: <mailto:qt4-preview-feedback-request@trolltech.com?subject=subscribe>
• List-unsubscribe: <mailto:qt4-preview-feedback-request@trolltech.com?subject=unsubscribe>
• Resent-from: qt4-preview-feedback@xxxxxxxxxxxxx
• Resent-message-id: <_hbi0C.A.l5C.lwEQGB@esparsett>
• Resent-sender: qt4-preview-feedback-request@xxxxxxxxxxxxx
• To: qt4-preview-feedback@xxxxxxxxxxxxx

most other classes have one signal for user related changes to the widget and 
one which includes programmatically changes as wel (like clicked() vs 
toggled(), avticated() vs. currentIndexChanged(),...)
Just QSpinBox does not have a signal for user changes, its valueChanged() 
covers both cases and editingFinished() does not quite cover this situation 
either

it would be nice to have such an additional signal there as well

Attachment:

Attachment: signature.asc
Description: This is a digitally signed message part.