diff options
Diffstat (limited to 'doc/html/moc.html')
| -rw-r--r-- | doc/html/moc.html | 42 |
1 files changed, 21 insertions, 21 deletions
diff --git a/doc/html/moc.html b/doc/html/moc.html index ad5bdd955..bbc07e574 100644 --- a/doc/html/moc.html +++ b/doc/html/moc.html @@ -55,11 +55,11 @@ use templates for signals and slots?</a>. <a name="1"></a><p> The moc is typically used with an input file containing class declarations like this: <p> <pre> - class MyClass : public <a href="qobject.html">TQObject</a> + class MyClass : public <a href="ntqobject.html">TQObject</a> { Q_OBJECT public: - MyClass( <a href="qobject.html">TQObject</a> * parent=0, const char * name=0 ); + MyClass( <a href="ntqobject.html">TQObject</a> * parent=0, const char * name=0 ); ~MyClass(); signals: @@ -80,13 +80,13 @@ case we declare a property of the enumeration type <tt>Priority</tt> that is also called "priority" and has a get function <tt>priority()</tt> and a set function <tt>setPriority()</tt>. <p> <pre> - class MyClass : public <a href="qobject.html">TQObject</a> + class MyClass : public <a href="ntqobject.html">TQObject</a> { Q_OBJECT Q_PROPERTY( Priority priority READ priority WRITE setPriority ) Q_ENUMS( Priority ) public: - MyClass( <a href="qobject.html">TQObject</a> * parent=0, const char * name=0 ); + MyClass( <a href="ntqobject.html">TQObject</a> * parent=0, const char * name=0 ); ~MyClass(); enum Priority { High, Low, VeryHigh, VeryLow }; @@ -100,13 +100,13 @@ macro. The Q_SETS macro declares enums that are to be used as sets, i.e. OR'ed together. Another macro, Q_CLASSINFO, can be used to attach additional name/value-pairs to the class' meta object: <p> <pre> - class MyClass : public <a href="qobject.html">TQObject</a> + class MyClass : public <a href="ntqobject.html">TQObject</a> { Q_OBJECT Q_CLASSINFO( "Author", "Oscar Peterson") Q_CLASSINFO( "Status", "Active") public: - MyClass( <a href="qobject.html">TQObject</a> * parent=0, const char * name=0 ); + MyClass( <a href="ntqobject.html">TQObject</a> * parent=0, const char * name=0 ); ~MyClass(); }; </pre> @@ -205,7 +205,7 @@ that file are fully known. <tr bgcolor="#d0d0d0"> <td valign="top">-f <td valign="top">Force the generation of an #include statement in the -output. This is the default for files whose name matches the <a href="qregexp.html#regular-expression">regular expression</a> \.[hH][^.]* (i.e. the extension starts with H or h). This +output. This is the default for files whose name matches the <a href="ntqregexp.html#regular-expression">regular expression</a> \.[hH][^.]* (i.e. the extension starts with H or h). This option is only useful if you have header files that do not follow the standard naming conventions. <tr bgcolor="#f0f0f0"> @@ -254,7 +254,7 @@ not usually a problem in practice. <p> The moc does not handle all of C++. The main problem is that class templates cannot have signals or slots. Here is an example: <p> <pre> - class SomeTemplate<int> : public <a href="qframe.html">TQFrame</a> { + class SomeTemplate<int> : public <a href="ntqframe.html">TQFrame</a> { Q_OBJECT ... signals: @@ -265,13 +265,13 @@ templates cannot have signals or slots. Here is an example: <p> Less importantly, the following constructs are illegal. All of them have alternatives which we think are usually better, so removing these limitations is not a high priority for us. -<p> <h3> Multiple inheritance requires <a href="qobject.html">TQObject</a> to be first +<p> <h3> Multiple inheritance requires <a href="ntqobject.html">TQObject</a> to be first </h3> <a name="5-1"></a><p> If you are using multiple inheritance, moc assumes that the <em>first</em> inherited class is a subclass of TQObject. Also, be sure that <em>only</em> the first inherited class is a TQObject. <p> <pre> - class SomeClass : public <a href="qobject.html">TQObject</a>, public OtherClass { + class SomeClass : public <a href="ntqobject.html">TQObject</a>, public OtherClass { ... }; </pre> @@ -285,7 +285,7 @@ is a TQObject.) signal/slot arguments, we think inheritance is a better alternative. Here is an example of illegal syntax: <p> <pre> - class SomeClass : public <a href="qobject.html">TQObject</a> { + class SomeClass : public <a href="ntqobject.html">TQObject</a> { Q_OBJECT ... public slots: @@ -298,7 +298,7 @@ Here is an example of illegal syntax: <pre> typedef void (*ApplyFunctionType)( List *, void * ); - class SomeClass : public <a href="qobject.html">TQObject</a> { + class SomeClass : public <a href="ntqobject.html">TQObject</a> { Q_OBJECT ... public slots: @@ -315,7 +315,7 @@ placed in signals or slots sections. Put them in the private, protected or public sections instead. Here is an example of the illegal syntax: <p> <pre> - class SomeClass : public <a href="qobject.html">TQObject</a> { + class SomeClass : public <a href="ntqobject.html">TQObject</a> { Q_OBJECT ... signals: @@ -329,10 +329,10 @@ illegal syntax: public status is not extended to cover signals and slots. Here is an illegal example: <p> <pre> - class Whatever : public <a href="qbuttongroup.html">TQButtonGroup</a> { + class Whatever : public <a href="ntqbuttongroup.html">TQButtonGroup</a> { ... public slots: - <a href="qbuttongroup.html">TQButtonGroup</a>::buttonPressed; // WRONG + <a href="ntqbuttongroup.html">TQButtonGroup</a>::buttonPressed; // WRONG ... }; </pre> @@ -356,7 +356,7 @@ will not work in signals and slots. Here is an illegal example: #define SIGNEDNESS(a) a #endif - class Whatever : public <a href="qobject.html">TQObject</a> { + class Whatever : public <a href="ntqobject.html">TQObject</a> { ... signals: void someSignal( SIGNEDNESS(int) ); @@ -394,11 +394,11 @@ that it happens to work in some cases). Put them in private, protected or public sections, where they belong. Here is an example of the illegal syntax: <p> <pre> - class SomeClass : public <a href="qobject.html">TQObject</a> { + class SomeClass : public <a href="ntqobject.html">TQObject</a> { Q_OBJECT public slots: - SomeClass( <a href="qobject.html">TQObject</a> *parent, const char *name ) - : <a href="qobject.html">TQObject</a>( parent, name ) { } // WRONG + SomeClass( <a href="ntqobject.html">TQObject</a> *parent, const char *name ) + : <a href="ntqobject.html">TQObject</a>( parent, name ) { } // WRONG ... }; </pre> @@ -412,7 +412,7 @@ does not work as expected. The moc will complain that it can neither find the functions nor resolve the type. Here is an example of the illegal syntax: <p> <pre> - class SomeClass : public <a href="qobject.html">TQObject</a> { + class SomeClass : public <a href="ntqobject.html">TQObject</a> { Q_OBJECT public: ... @@ -428,7 +428,7 @@ illegal syntax: <p> Work around this limitation by declaring all properties at the beginning of the class declaration, right after Q_OBJECT: <p> <pre> - class SomeClass : public <a href="qobject.html">TQObject</a> { + class SomeClass : public <a href="ntqobject.html">TQObject</a> { Q_OBJECT Q_PROPERTY( Priority priority READ priority WRITE setPriority ) Q_ENUMS( Priority ) |