diff options
Diffstat (limited to 'doc/plugins-howto.doc')
| -rw-r--r-- | doc/plugins-howto.doc | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/doc/plugins-howto.doc b/doc/plugins-howto.doc index b7ab64454..aaada79fe 100644 --- a/doc/plugins-howto.doc +++ b/doc/plugins-howto.doc @@ -67,7 +67,7 @@ by default in the standard plugin directory. \i \l TQSqlDriverPlugin \i \c{pluginsbase/sqldrivers} <sup>*</sup> \row -\i \l QStylePlugin +\i \l TQStylePlugin \i \c{pluginsbase/styles} <sup>*</sup> \row \i \l TQTextCodecPlugin @@ -92,7 +92,7 @@ set your own path or paths you can use Suppose that you have a new style class called 'MyStyle' that you want to make available as a plugin. The required code is straightforward: \code - class MyStylePlugin : public QStylePlugin + class MyStylePlugin : public TQStylePlugin { public: MyStylePlugin() {} @@ -102,7 +102,7 @@ to make available as a plugin. The required code is straightforward: return TQStringList() << "mystyle"; } - QStyle* create( const TQString& key ) { + TQStyle* create( const TQString& key ) { if ( key == "mystyle" ) return new MyStyle; return 0; @@ -112,7 +112,7 @@ to make available as a plugin. The required code is straightforward: TQ_EXPORT_PLUGIN( MyStylePlugin ) \endcode -(Note that QStyleFactory is case-insensitive, and the lower case +(Note that TQStyleFactory is case-insensitive, and the lower case version of the key is used; other factories, e.g. TQWidgetFactory, are case sensitive.) @@ -122,19 +122,19 @@ The first is keys() which returns a string list of the classes implemented in the plugin. (We've just implemented one class in the example above.) The second is a function that returns an object of the required class (or 0 if the plugin is asked to create an object of a -class that it doesn't implement). For QStylePlugin, this second +class that it doesn't implement). For TQStylePlugin, this second function is called create(). It is possible to implement any number of plugin subclasses in a single plugin, providing they are all derived from the same base -class, e.g. QStylePlugin. +class, e.g. TQStylePlugin. For database drivers, image formats, custom widgets and text codecs, 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( QStyleFactory::create( "MyStyle" ) ); + QApplication::setStyle( TQStyleFactory::create( "MyStyle" ) ); \endcode Some plugin classes require additional functions to be implemented. |