diff options
Diffstat (limited to 'doc/html/plugins-howto.html')
| -rw-r--r-- | doc/html/plugins-howto.html | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/html/plugins-howto.html b/doc/html/plugins-howto.html index 05502bd31..c9182a9f8 100644 --- a/doc/html/plugins-howto.html +++ b/doc/html/plugins-howto.html @@ -62,13 +62,13 @@ by default in the standard plugin directory. </table></center> <p> But where is the <tt>pluginsbase</tt> directory? When the application is run, TQt will first treat the application's executable directory as the -<tt>pluginsbase</tt>. For example if the application is in <tt>C:\Program Files\MyApp</tt> and has a style plugin, TQt will look in <tt>C:\Program Files\MyApp\styles</tt>. (See <a href="ntqapplication.html#applicationDirPath">TQApplication::applicationDirPath</a>() for +<tt>pluginsbase</tt>. For example if the application is in <tt>C:\Program Files\MyApp</tt> and has a style plugin, TQt will look in <tt>C:\Program Files\MyApp\styles</tt>. (See <a href="tqapplication.html#applicationDirPath">TQApplication::applicationDirPath</a>() for how to find out where the application's executable is.) TQt will also look in the directory given by <tt>tqInstallPathPlugins()</tt>. If you want TQt to look in additional places you can add as many paths as you need -with calls to <a href="ntqapplication.html#addLibraryPath">TQApplication::addLibraryPath</a>(). And if you want to +with calls to <a href="tqapplication.html#addLibraryPath">TQApplication::addLibraryPath</a>(). And if you want to set your own path or paths you can use -<a href="ntqapplication.html#setLibraryPaths">TQApplication::setLibraryPaths</a>(). +<a href="tqapplication.html#setLibraryPaths">TQApplication::setLibraryPaths</a>(). <p> Suppose that you have a new style class called 'MyStyle' that you want to make available as a plugin. The required code is straightforward: <pre> @@ -111,7 +111,7 @@ no explicit object creation is required. TQt will find and create them as required. Styles are an exception, since you might want to set a style explicitly in code. To apply a style, use code like this: <pre> - TQApplication::<a href="ntqapplication.html#setStyle">setStyle</a>( TQStyleFactory::<a href="tqstylefactory.html#create">create</a>( "MyStyle" ) ); + TQApplication::<a href="tqapplication.html#setStyle">setStyle</a>( TQStyleFactory::<a href="tqstylefactory.html#create">create</a>( "MyStyle" ) ); </pre> <p> Some plugin classes require additional functions to be implemented. @@ -132,7 +132,7 @@ with each type of plugin in a subdirectory for that type, e.g. <tt>styles</tt>. 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, e.g. using <a href="tqsettings.html">TQSettings</a>, for the application to read when it runs. The -application can then call <a href="ntqapplication.html#addLibraryPath">TQApplication::addLibraryPath</a>() with this +application can then call <a href="tqapplication.html#addLibraryPath">TQApplication::addLibraryPath</a>() with this path and your plugins will be available to the application. Note that the final part of the path, i.e. <tt>styles</tt>, <tt>widgets</tt>, etc., cannot be changed. |