QSpinBox or QLabels

[bender86]

Try this way:

QSpinBox box;
box.setButtonSymbols(QAbstractSpinBox::NoButtons);
box.setReadOnly(true);

QSpinBox box;
box.setButtonSymbols(QAbstractSpinBox::NoButtons);
box.setReadOnly(true);

To copy to clipboard, switch view to plain text mode 

[ToddAtWSU]

box.setButtonSymbols(QAbstractSpinBox::NoButtons);[/CODE]

Where do you see QAbstractSpinBox::NoButtons? All I see is QAbstractSpinBox::UpDownArrows and QAbstractSpinBox::PlusMinus. I would imagine this worked but I do not see this anywhere in the docs. Thanks for your further clarification.

[jpn]

Where do you see QAbstractSpinBox::NoButtons?

It was introduced in Qt 4.3.

[ToddAtWSU]

It was introduced in Qt 4.3.

Thanks. I followed the other link and it was in 4.2. I am still unfortunately at 4.1. I know I need to upgrade soon...but can't right this minute. Thanks!

[wysota]

A read only spinbox yields no advantage over a regular line edit. The text is assembled every time you change it anyway, so there are no performance benefits of using QSpinBox over QLineEdit. And if you want to display something, you should use QLabel or friends, not QSpinBox or QLineEdit.

[ToddAtWSU]

A read only spinbox yields no advantage over a regular line edit. The text is assembled every time you change it anyway, so there are no performance benefits of using QSpinBox over QLineEdit. And if you want to display something, you should use QLabel or friends, not QSpinBox or QLineEdit.

The only advantage I am looking for is so I don't have to remember to add the label to my QLabel every time I change it. With the SpinBox's suffix feature, this allows me to just change the value and never worry about forgetting to add the suffix at the end of my label.

[wysota]

What kind of argument is this? Ever heard of functions or methods?

[ToddAtWSU]

haha...yeah I just never think of writing functions for something so simple like that...i admit a bad argument and I think i will just write a simple function!

[wysota]

My point is that you should use proper components for proper tasks. For example you shouldn't use a combobox if you have only two choices - use radio buttons or a checkbox instead. If you want to display text, don't use input widgets. These are rules of good ui design.