diff options
Diffstat (limited to 'doc/html/signalsandslots.html')
-rw-r--r-- | doc/html/signalsandslots.html | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/html/signalsandslots.html b/doc/html/signalsandslots.html index 19e238065..116cd27b1 100644 --- a/doc/html/signalsandslots.html +++ b/doc/html/signalsandslots.html @@ -201,7 +201,7 @@ is emitted. and must not be implemented in the <tt>.cpp</tt> file. They can never have return types (i.e. use <tt>void</tt>). <p> A note about arguments. Our experience shows that signals and slots -are more reusable if they do <em>not</em> use special types. If <a href="ntqscrollbar.html#valueChanged">TQScrollBar::valueChanged</a>() were to use a special type such as the +are more reusable if they do <em>not</em> use special types. If <a href="tqscrollbar.html#valueChanged">TQScrollBar::valueChanged</a>() were to use a special type such as the hypothetical <tt>TQRangeControl::Range</tt>, it could only be connected to slots designed specifically for <a href="ntqrangecontrol.html">TQRangeControl</a>. Something as simple as the program in <a href="tutorial1-05.html">Tutorial #1 part 5</a> @@ -270,7 +270,7 @@ doesn't TQt use templates for signals and slots?</a>.) <p> <h2> A Real Example </h2> -<a name="5"></a><p> Here is a simple commented example (code fragments from <a href="qlcdnumber-h.html">ntqlcdnumber.h</a> ). +<a name="5"></a><p> Here is a simple commented example (code fragments from <a href="tqlcdnumber-h.html">tqlcdnumber.h</a> ). <p> <pre> #include "ntqframe.h" #include "tqbitarray.h" @@ -278,7 +278,7 @@ doesn't TQt use templates for signals and slots?</a>.) class TQLCDNumber : public <a href="ntqframe.html">TQFrame</a> </pre> -<p> <a href="ntqlcdnumber.html">TQLCDNumber</a> inherits <a href="tqobject.html">TQObject</a>, which has most of the signal/slot +<p> <a href="tqlcdnumber.html">TQLCDNumber</a> inherits <a href="tqobject.html">TQObject</a>, which has most of the signal/slot knowledge, via <a href="ntqframe.html">TQFrame</a> and <a href="tqwidget.html">TQWidget</a>, and #include's the relevant declarations. <p> <pre> @@ -293,7 +293,7 @@ you have probably forgotten to <a href="moc.html">run the moc</a> or to include the moc output in the link command. <p> <pre> public: - <a href="ntqlcdnumber.html">TQLCDNumber</a>( <a href="tqwidget.html">TQWidget</a> *parent=0, const char *name=0 ); + <a href="tqlcdnumber.html">TQLCDNumber</a>( <a href="tqwidget.html">TQWidget</a> *parent=0, const char *name=0 ); TQLCDNumber( uint numDigits, TQWidget *parent=0, const char *name=0 ); </pre> @@ -308,7 +308,7 @@ ignores member functions. void overflow(); </pre> -<p> <a href="ntqlcdnumber.html">TQLCDNumber</a> emits a signal when it is asked to show an impossible +<p> <a href="tqlcdnumber.html">TQLCDNumber</a> emits a signal when it is asked to show an impossible value. <p> If you don't care about overflow, or you know that overflow cannot occur, you can ignore the overflow() signal, i.e. don't connect it to @@ -334,7 +334,7 @@ indicates, to set the displayed number. Since <tt>display()</tt> is part of the class's interface with the rest of the program, the slot is public. <p> Several of the example programs connect the newValue() signal of a -<a href="ntqscrollbar.html">TQScrollBar</a> to the display() slot, so the LCD number continuously shows +<a href="tqscrollbar.html">TQScrollBar</a> to the display() slot, so the LCD number continuously shows the value of the scroll bar. <p> Note that display() is overloaded; TQt will select the appropriate version when you connect a signal to the slot. With callbacks, you'd have to find |