summaryrefslogtreecommitdiffstats
path: root/doc/html/designer-manual-16.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/html/designer-manual-16.html')
-rw-r--r--doc/html/designer-manual-16.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/html/designer-manual-16.html b/doc/html/designer-manual-16.html
index 39513c565..b156e25c8 100644
--- a/doc/html/designer-manual-16.html
+++ b/doc/html/designer-manual-16.html
@@ -182,7 +182,7 @@ body { background: #ffffff; color: black; }
</pre>
<a name="exportmacro"></a><h4><a name="1-7"></a>exportmacro</h4>
<p>This tag is only relevant to Windows users.</p>
-<p>If you have a class that requires some Windows-specific export macro, e.g. for classes in a DLL that need to be declared like this: <tt>class win_specific_declaration_goes_here Class</tt>, you can use the <tt>&lt;exportmacro&gt;</tt> tag. (In standard TQt we use the <tt>Q_EXPORT</tt> macro, e.g. <tt>class Q_EXPORT TQWidget</tt>.) If you use this tag you must also:</p>
+<p>If you have a class that requires some Windows-specific export macro, e.g. for classes in a DLL that need to be declared like this: <tt>class win_specific_declaration_goes_here Class</tt>, you can use the <tt>&lt;exportmacro&gt;</tt> tag. (In standard TQt we use the <tt>TQ_EXPORT</tt> macro, e.g. <tt>class TQ_EXPORT TQWidget</tt>.) If you use this tag you must also:</p>
<ol type=1><li><p><a href="designer-manual-16.html#1-11">include</a> the file which contains the macro definition;</p>
<li><p>add the export macro to the form -- this is achieved by entering the macro's name in the 'export macro' sub-property of the form's name property.</p>
</ol><p>Following these steps will ensure that <a href="uic.html">uic</a> will create the correct <tt>class YOUR_MACRO Form</tt> declarations.</p>