diff options
Diffstat (limited to 'doc/html/signalsandslots.html')
| -rw-r--r-- | doc/html/signalsandslots.html | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/doc/html/signalsandslots.html b/doc/html/signalsandslots.html index 1ea4a9f1..5691cd3d 100644 --- a/doc/html/signalsandslots.html +++ b/doc/html/signalsandslots.html @@ -171,11 +171,11 @@ about each other, as long as there is someone around to set up a connection between them initially. <p> The preprocessor changes or removes the <tt>signals</tt>, <tt>slots</tt> and <tt>emit</tt> keywords so that the compiler is presented with standard C++. -<p> Run the <a href="moc.html">moc</a> on class definitions that contain +<p> Run the <a href="tqmoc.html">tqmoc</a> on class definitions that contain signals or slots. This produces a C++ source file which should be compiled and linked with the other object files for the application. If you use <a href="qmake-manual.html">qmake</a>, the makefile rules to -automatically invoke the <a href="moc.html">moc</a> will be added to +automatically invoke the <a href="tqmoc.html">tqmoc</a> will be added to your makefile for you. <p> <h2> Signals </h2> @@ -197,7 +197,7 @@ mechanism is totally independent of any GUI event loop. The <p> If several slots are connected to one signal, the slots will be executed one after the other, in an arbitrary order, when the signal is emitted. -<p> Signals are automatically generated by the <a href="moc.html">moc</a> +<p> Signals are automatically generated by the <a href="tqmoc.html">tqmoc</a> 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 @@ -254,7 +254,7 @@ the signals and slots mechanism is well worth the overhead, which your users won't even notice. <p> <h2> Meta Object Information </h2> -<a name="4"></a><p> The <a href="metaobjects.html#meta-object">meta object</a> compiler (<a href="moc.html"><a href="moc.html#moc">moc</a></a>) parses the class +<a name="4"></a><p> The <a href="metaobjects.html#meta-object">meta object</a> compiler (<a href="tqmoc.html"><a href="tqmoc.html#tqmoc">tqmoc</a></a>) parses the class declaration in a C++ file and generates C++ code that initializes the meta object. The meta object contains the names of all the signal and slot members, as well as pointers to these functions. (For more @@ -287,21 +287,21 @@ declarations. </pre> <p> TQ_OBJECT is expanded by the preprocessor to declare several member -functions that are implemented by the moc; if you get compiler errors +functions that are implemented by tqmoc; if you get compiler errors along the lines of "virtual function TQButton::className not defined" -you have probably forgotten to <a href="moc.html">run the moc</a> or to -include the moc output in the link command. +you have probably forgotten to <a href="tqmoc.html">run tqmoc</a> or to +include tqmoc output in the link command. <p> <pre> public: <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> -<p> It's not obviously relevant to the moc, but if you inherit TQWidget you +<p> It's not obviously relevant to tqmoc, but if you inherit TQWidget you almost certainly want to have the <em>parent</em> and <em>name</em> arguments in your constructors, and pass them to the parent constructor. -<p> Some destructors and member functions are omitted here; the moc +<p> Some destructors and member functions are omitted here; tqmoc ignores member functions. <p> <pre> signals: |