summaryrefslogtreecommitdiffstats
path: root/doc/html/plugins-howto.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/html/plugins-howto.html')
-rw-r--r--doc/html/plugins-howto.html6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/html/plugins-howto.html b/doc/html/plugins-howto.html
index 1e91156d4..7bb3a2dcd 100644
--- a/doc/html/plugins-howto.html
+++ b/doc/html/plugins-howto.html
@@ -128,7 +128,7 @@ must be reimplemented for each type of plugin.
because plugins are stored in the standard plugin subdirectories.
Because of this applications don't require any code to find and load
plugins, since TQt handles them automatically.
-<p> The default directory for plugins is <tt>QTDIR/plugins</tt><sup>*</sup>,
+<p> The default directory for plugins is <tt>TQTDIR/plugins</tt><sup>*</sup>,
with each type of plugin in a subdirectory for that type, e.g. <tt>styles</tt>. If you want your applications to use plugins and you don't
want to use the standard plugins path, have your installation process
determine the path you want to use for the plugins, and save the path,
@@ -143,9 +143,9 @@ compile it in with the application, or to compile it into a <tt>DLL</tt> (or
other library. If you want the plugin to be loadable then one approach
is to create a subdirectory under the application, e.g. <tt>appdir/plugins/designer</tt>, and place the plugin in that directory.
<p> For <a href="designer-manual.html">TQt Designer</a>, you may need to
-call TQApplication::addLibraryPath("QTDIR/plugins/designer") to load
+call TQApplication::addLibraryPath("TQTDIR/plugins/designer") to load
your <a href="designer-manual.html">TQt Designer</a> plugins.
-<p> <sup>*</sup><small> All references to <tt>QTDIR</tt> refer to the path
+<p> <sup>*</sup><small> All references to <tt>TQTDIR</tt> refer to the path
where TQt was installed. </small>
<p> <h2> Loading and Verifying Plugins
</h2>