diff options
Diffstat (limited to 'doc/plugins-howto.doc')
| -rw-r--r-- | doc/plugins-howto.doc | 12 | 
1 files changed, 6 insertions, 6 deletions
| diff --git a/doc/plugins-howto.doc b/doc/plugins-howto.doc index 71d1314af..96368fedc 100644 --- a/doc/plugins-howto.doc +++ b/doc/plugins-howto.doc @@ -81,13 +81,13 @@ But where is the \c{pluginsbase} directory? When the application is  run, TQt will first treat the application's executable directory as the  \c{pluginsbase}. For example if the application is in \c{C:\Program  Files\MyApp} and has a style plugin, TQt will look in \c{C:\Program -Files\MyApp\styles}. (See \l{QApplication::applicationDirPath()} for +Files\MyApp\styles}. (See \l{TQApplication::applicationDirPath()} for  how to find out where the application's executable is.) TQt will also  look in the directory given by \c{tqInstallPathPlugins()}. If you want  Qt to look in additional places you can add as many paths as you need -with calls to \c{QApplication::addLibraryPath()}. And if you want to +with calls to \c{TQApplication::addLibraryPath()}. And if you want to  set your own path or paths you can use -\c{QApplication::setLibraryPaths()}. +\c{TQApplication::setLibraryPaths()}.  Suppose that you have a new style class called 'MyStyle' that you want  to make available as a plugin. The required code is straightforward: @@ -134,7 +134,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:  \code -    QApplication::setStyle( TQStyleFactory::create( "MyStyle" ) ); +    TQApplication::setStyle( TQStyleFactory::create( "MyStyle" ) );  \endcode  Some plugin classes require additional functions to be implemented. @@ -159,7 +159,7 @@ styles. 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,  e.g. using TQSettings, for the application to read when it runs. The -application can then call QApplication::addLibraryPath() with this +application can then call TQApplication::addLibraryPath() with this  path and your plugins will be available to the application. Note that  the final part of the path, i.e. \c styles, \c widgets, etc., cannot  be changed. @@ -172,7 +172,7 @@ is to create a subdirectory under the application, e.g. \c  appdir/plugins/designer, and place the plugin in that directory.  For \link designer-manual.book TQt Designer\endlink, you may need to -call QApplication::addLibraryPath("TQTDIR/plugins/designer") to load +call TQApplication::addLibraryPath("TQTDIR/plugins/designer") to load  your \link designer-manual.book TQt Designer\endlink plugins.  <sup>*</sup><small> All references to \c{TQTDIR} refer to the path | 
