1 files changed, 12 insertions, 12 deletions
diff --git a/doc/man/man3/tqwidgetfactory.3qt b/doc/man/man3/tqwidgetfactory.3qt
index a634bad5..23e0f8c5 100644
--- a/doc/man/man3/tqwidgetfactory.3qt
+++ b/doc/man/man3/tqwidgetfactory.3qt
@@ -20,28 +20,28 @@ QWidgetFactory \- For the dynamic creation of widgets from TQt Designer .ui file
 .BI "virtual \fB~QWidgetFactory\fR ()"
 .br
 .ti -1c
-.BI "virtual QWidget * \fBcreateWidget\fR ( const QString & className, QWidget * parent, const char * name ) const"
+.BI "virtual TQWidget * \fBcreateWidget\fR ( const TQString & className, TQWidget * parent, const char * name ) const"
 .br
 .in -1c
 .SS "Static Public Members"
 .in +1c
 .ti -1c
-.BI "QWidget * \fBcreate\fR ( const QString & uiFile, QObject * connector = 0, QWidget * parent = 0, const char * name = 0 )"
+.BI "TQWidget * \fBcreate\fR ( const TQString & uiFile, TQObject * connector = 0, TQWidget * parent = 0, const char * name = 0 )"
 .br
 .ti -1c
-.BI "QWidget * \fBcreate\fR ( QIODevice * dev, QObject * connector = 0, QWidget * parent = 0, const char * name = 0 )"
+.BI "TQWidget * \fBcreate\fR ( TQIODevice * dev, TQObject * connector = 0, TQWidget * parent = 0, const char * name = 0 )"
 .br
 .ti -1c
 .BI "void \fBaddWidgetFactory\fR ( QWidgetFactory * factory )"
 .br
 .ti -1c
-.BI "void \fBloadImages\fR ( const QString & dir )"
+.BI "void \fBloadImages\fR ( const TQString & dir )"
 .br
 .ti -1c
 .BI "QStringList \fBwidgets\fR ()"
 .br
 .ti -1c
-.BI "bool \fBsupportsWidget\fR ( const QString & widget )"
+.BI "bool \fBsupportsWidget\fR ( const TQString & widget )"
 .br
 .in -1c
 .SH DESCRIPTION
@@ -50,7 +50,7 @@ The QWidgetFactory class provides for the dynamic creation of widgets from TQt D
 This class basically offers two things:
 .IP
 .TP
-Dynamically creating widgets from TQt Designer user interface description files. You can do this using the static function QWidgetFactory::create(). This function also performs signal and slot connections, tab ordering, etc., as defined in the .ui file, and returns the top-level widget in the .ui file. After creating the widget you can use QObject::child() and QObject::queryList() to access child widgets of this returned widget.
+Dynamically creating widgets from TQt Designer user interface description files. You can do this using the static function QWidgetFactory::create(). This function also performs signal and slot connections, tab ordering, etc., as defined in the .ui file, and returns the top-level widget in the .ui file. After creating the widget you can use TQObject::child() and TQObject::queryList() to access child widgets of this returned widget.
 .IP
 .TP
 Adding additional widget factories to be able to create custom widgets. See createWidget() for details.
@@ -68,19 +68,19 @@ Constructs a QWidgetFactory.
 Destructor.
 .SH "void QWidgetFactory::addWidgetFactory ( QWidgetFactory * factory )\fC [static]\fR"
 Installs a widget factory \fIfactory\fR, which normally contains additional widgets that can then be created using a QWidgetFactory. See createWidget() for further details.
-.SH "QWidget * QWidgetFactory::create ( const QString & uiFile, QObject * connector = 0, QWidget * parent = 0, const char * name = 0 )\fC [static]\fR"
+.SH "TQWidget * QWidgetFactory::create ( const TQString & uiFile, TQObject * connector = 0, TQWidget * parent = 0, const char * name = 0 )\fC [static]\fR"
 Loads the \fIQt Designer\fR user interface description file \fIuiFile\fR and returns the top-level widget in that description. \fIparent\fR and \fIname\fR are passed to the constructor of the top-level widget.
 .PP
-This function also performs signal and slot connections, tab ordering, etc., as described in the .ui file. In \fIQt Designer\fR it is possible to add custom slots to a form and connect to them. If you want these connections to be made, you must create a class derived from QObject, which implements all these slots. Then pass an instance of the object as \fIconnector\fR to this function. If you do this, the connections to the custom slots will be done using the \fIconnector\fR as slot.
+This function also performs signal and slot connections, tab ordering, etc., as described in the .ui file. In \fIQt Designer\fR it is possible to add custom slots to a form and connect to them. If you want these connections to be made, you must create a class derived from TQObject, which implements all these slots. Then pass an instance of the object as \fIconnector\fR to this function. If you do this, the connections to the custom slots will be done using the \fIconnector\fR as slot.
 .PP
 If something fails, 0 is returned.
 .PP
 The ownership of the returned widget is passed to the caller.
-.SH "QWidget * QWidgetFactory::create ( QIODevice * dev, QObject * connector = 0, QWidget * parent = 0, const char * name = 0 )\fC [static]\fR"
+.SH "TQWidget * QWidgetFactory::create ( TQIODevice * dev, TQObject * connector = 0, TQWidget * parent = 0, const char * name = 0 )\fC [static]\fR"
 This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
 .PP
 Loads the user interface description from device \fIdev\fR.
-.SH "QWidget * QWidgetFactory::createWidget ( const QString & className, QWidget * parent, const char * name ) const\fC [virtual]\fR"
+.SH "TQWidget * QWidgetFactory::createWidget ( const TQString & className, TQWidget * parent, const char * name ) const\fC [virtual]\fR"
 Creates a widget of the type \fIclassName\fR passing \fIparent\fR and \fIname\fR to its constructor.
 .PP
 If \fIclassName\fR is a widget in the TQt library, it is directly created by this function. If the widget isn't in the TQt library, each of the installed widget plugins is asked, in turn, to create the widget. As soon as a plugin says it can create the widget it is asked to do so. It may occur that none of the plugins can create the widget, in which case each installed widget factory is asked to create the widget (see addWidgetFactory()). If the widget cannot be created by any of these means, 0 is returned.
@@ -102,9 +102,9 @@ Subclass QWidgetFactory. Then reimplement this function to create and return an
 .fi
 where MyWidgetFactory is your QWidgetFactory subclass.
 .IP
-.SH "void QWidgetFactory::loadImages ( const QString & dir )\fC [static]\fR"
+.SH "void QWidgetFactory::loadImages ( const TQString & dir )\fC [static]\fR"
 If you use a pixmap collection (which is the default for new projects) rather than saving the pixmaps within the .ui XML file, you must load the pixmap collection. QWidgetFactory looks in the default QMimeSourceFactory for the pixmaps. Either add it there manually, or call this function and specify the directory where the images can be found, as \fIdir\fR. This is normally the directory called \fCimages\fR in the project's directory.
-.SH "bool QWidgetFactory::supportsWidget ( const QString & widget )\fC [static]\fR"
+.SH "bool QWidgetFactory::supportsWidget ( const TQString & widget )\fC [static]\fR"
 Returns TRUE if the widget factory can create the specified \fIwidget\fR; otherwise returns FALSE.
 .SH "QStringList QWidgetFactory::widgets ()\fC [static]\fR"
 Returns the names of the widgets this factory can create.