This file is mainly lifted from Chapter 6; only the non-trivial changes are noted here.

+

<!--T:12-->

+

This file is mainly lifted from [[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_06|Chapter 6]]; only the non-trivial changes are noted here.

</translate>

</translate>

Line 52:

Line 61:

<translate>

<translate>

+

<!--T:13-->

These make up an interface between this widget and other components in a program. Until now, '''<tt>LCDRange</tt>''' didn't really have an API at all.

These make up an interface between this widget and other components in a program. Until now, '''<tt>LCDRange</tt>''' didn't really have an API at all.

+

<!--T:14-->

'''<tt>value()</tt>''' is a public function for accessing the value of the '''<tt>LCDRange</tt>''', '''<tt>setValue()</tt>''' is our first custom slot, and '''<tt>valueChanged()</tt>''' is our first custom signal.

'''<tt>value()</tt>''' is a public function for accessing the value of the '''<tt>LCDRange</tt>''', '''<tt>setValue()</tt>''' is our first custom slot, and '''<tt>valueChanged()</tt>''' is our first custom signal.

+

<!--T:15-->

Slots must be implemented in the normal way (a slot is also a Ruby member function). Signals are automatically implemented. Signals follow the access rules of protected Ruby functions (i.e., they can be emitted only by the class they are defined in or by classes inheriting from it).

Slots must be implemented in the normal way (a slot is also a Ruby member function). Signals are automatically implemented. Signals follow the access rules of protected Ruby functions (i.e., they can be emitted only by the class they are defined in or by classes inheriting from it).

+

<!--T:16-->

The '''<tt>valueChanged()</tt>''' signal is used when the '''<tt>LCDRange's</tt>''' value has changed.

The '''<tt>valueChanged()</tt>''' signal is used when the '''<tt>LCDRange's</tt>''' value has changed.

+

<!--T:17-->

The implementation of '''<tt>value()</tt>''' is straightforward. It simply returns the slider's value.

The implementation of '''<tt>value()</tt>''' is straightforward. It simply returns the slider's value.

+

<!--T:18-->

The implementation of '''<tt>setValue()</tt>''' is equally straightforward. Note that because the slider and LCD number are connected, setting the slider's value automatically updates the LCD number as well. In addition, the slider will automatically adjust the value if it is outside its legal range.

The implementation of '''<tt>setValue()</tt>''' is equally straightforward. Note that because the slider and LCD number are connected, setting the slider's value automatically updates the LCD number as well. In addition, the slider will automatically adjust the value if it is outside its legal range.

</translate>

</translate>

Line 73:

Line 88:

<translate>

<translate>

+

<!--T:19-->

The first [http://doc.qt.nokia.com/latest/qobject.html#connect QObject::connect()] call is the same that you have seen in the previous chapter. The second is new; it connects slider's [http://doc.qt.nokia.com/latest/qabstractslider.html#valueChanged QAbstractSlider::valueChanged()] signal to this object's '''<tt>valueChanged()</tt>''' signal. Yes, that's right. Signals can be connected to other signals. When the first is emitted, the second signal is also emitted.

The first [http://doc.qt.nokia.com/latest/qobject.html#connect QObject::connect()] call is the same that you have seen in the previous chapter. The second is new; it connects slider's [http://doc.qt.nokia.com/latest/qabstractslider.html#valueChanged QAbstractSlider::valueChanged()] signal to this object's '''<tt>valueChanged()</tt>''' signal. Yes, that's right. Signals can be connected to other signals. When the first is emitted, the second signal is also emitted.

+

<!--T:20-->

Let's look at what happens when the user operates the slider. The slider sees that its value has changed and emits the [http://doc.qt.nokia.com/latest/qabstractslider.html#valueChanged QAbstractSlider::valueChanged()] signal. That signal is connected both to the [http://doc.qt.nokia.com/latest/qlcdnumber.html#intValue-prop QLCDNumber::display()] slot of the [http://doc.qt.nokia.com/latest/qlcdnumber.html Qt::LCDNumber] and to the '''<tt>valueChanged()</tt>''' signal of the '''<tt>LCDRange</tt>'''.

Let's look at what happens when the user operates the slider. The slider sees that its value has changed and emits the [http://doc.qt.nokia.com/latest/qabstractslider.html#valueChanged QAbstractSlider::valueChanged()] signal. That signal is connected both to the [http://doc.qt.nokia.com/latest/qlcdnumber.html#intValue-prop QLCDNumber::display()] slot of the [http://doc.qt.nokia.com/latest/qlcdnumber.html Qt::LCDNumber] and to the '''<tt>valueChanged()</tt>''' signal of the '''<tt>LCDRange</tt>'''.

+

<!--T:21-->

Thus, when the signal is emitted, '''<tt>LCDRange</tt>''' emits its own '''<tt>valueChanged()</tt>''' signal. In addition, [http://doc.qt.nokia.com/latest/qlcdnumber.html#intValue-prop QLCDNumber::display()] is called and shows the new number.

Thus, when the signal is emitted, '''<tt>LCDRange</tt>''' emits its own '''<tt>valueChanged()</tt>''' signal. In addition, [http://doc.qt.nokia.com/latest/qlcdnumber.html#intValue-prop QLCDNumber::display()] is called and shows the new number.

+

<!--T:22-->

Note that you're not guaranteed any particular order of execution; '''<tt>LCDRange::valueChanged()</tt>''' may be emitted before or after [http://doc.qt.nokia.com/latest/qlcdnumber.html#intValue-prop QLCDNumber::display()] is called.

Note that you're not guaranteed any particular order of execution; '''<tt>LCDRange::valueChanged()</tt>''' may be emitted before or after [http://doc.qt.nokia.com/latest/qlcdnumber.html#intValue-prop QLCDNumber::display()] is called.

</translate>

</translate>

Line 100:

Line 119:

<translate>

<translate>

+

<!--T:23-->

When we create the nine '''<tt>LCDRange</tt>''' objects, we connect them using the [http://doc.qt.nokia.com/latest/signalsandslots.html signals and slots] mechanism. Each has its '''<tt>valueChanged()</tt>''' signal connected to the previous one's '''<tt>setValue()</tt>''' slot. Because '''<tt>LCDRange</tt>''' emits the '''<tt>valueChanged()</tt>''' signal when its value changes, we are here creating a chain of signals and slots.

When we create the nine '''<tt>LCDRange</tt>''' objects, we connect them using the [http://doc.qt.nokia.com/latest/signalsandslots.html signals and slots] mechanism. Each has its '''<tt>valueChanged()</tt>''' signal connected to the previous one's '''<tt>setValue()</tt>''' slot. Because '''<tt>LCDRange</tt>''' emits the '''<tt>valueChanged()</tt>''' signal when its value changes, we are here creating a chain of signals and slots.

</translate>

</translate>

<translate>

<translate>

−

=== Running the Application ===

+

=== Running the Application === <!--T:24-->

+

<!--T:25-->

On startup, the program's appearance is identical to the previous one. Try operating the slider to the bottom-right.

On startup, the program's appearance is identical to the previous one. Try operating the slider to the bottom-right.

−

=== Exercises ===

+

=== Exercises === <!--T:26-->

+

<!--T:27-->

Use the bottom-right slider to set all LCDs to 50. Then set all but the last LCD to 40 by clicking once to the left of the bottom-middle slider handle. Now, use the bottom-left slider to set the first seven LCDs back to 50.

Use the bottom-right slider to set all LCDs to 50. Then set all but the last LCD to 40 by clicking once to the left of the bottom-middle slider handle. Now, use the bottom-left slider to set the first seven LCDs back to 50.

+

<!--T:28-->

Click to the left of the handle on the bottom-right slider. What happens? Why is this the correct behavior?

Click to the left of the handle on the bottom-right slider. What happens? Why is this the correct behavior?

These make up an interface between this widget and other components in a program. Until now, LCDRange didn't really have an API at all.

value() is a public function for accessing the value of the LCDRange, setValue() is our first custom slot, and valueChanged() is our first custom signal.

Slots must be implemented in the normal way (a slot is also a Ruby member function). Signals are automatically implemented. Signals follow the access rules of protected Ruby functions (i.e., they can be emitted only by the class they are defined in or by classes inheriting from it).

The valueChanged() signal is used when the LCDRange's value has changed.

The implementation of value() is straightforward. It simply returns the slider's value.

The implementation of setValue() is equally straightforward. Note that because the slider and LCD number are connected, setting the slider's value automatically updates the LCD number as well. In addition, the slider will automatically adjust the value if it is outside its legal range.

The first QObject::connect() call is the same that you have seen in the previous chapter. The second is new; it connects slider's QAbstractSlider::valueChanged() signal to this object's valueChanged() signal. Yes, that's right. Signals can be connected to other signals. When the first is emitted, the second signal is also emitted.

When we create the nine LCDRange objects, we connect them using the signals and slots mechanism. Each has its valueChanged() signal connected to the previous one's setValue() slot. Because LCDRange emits the valueChanged() signal when its value changes, we are here creating a chain of signals and slots.

Use the bottom-right slider to set all LCDs to 50. Then set all but the last LCD to 40 by clicking once to the left of the bottom-middle slider handle. Now, use the bottom-left slider to set the first seven LCDs back to 50.

Click to the left of the handle on the bottom-right slider. What happens? Why is this the correct behavior?