summaryrefslogtreecommitdiffstats
path: root/doc/man/man3
diff options
context:
space:
mode:
authorTimothy Pearson <[email protected]>2011-11-14 22:33:41 -0600
committerTimothy Pearson <[email protected]>2011-11-14 22:33:41 -0600
commit0f92dd542b65bc910caaf190b7c623aa5158c86a (patch)
tree120ab7e08fa0ffc354ef58d100f79a33c92aa6e6 /doc/man/man3
parentd796c9dd933ab96ec83b9a634feedd5d32e1ba3f (diff)
downloadtqt3-0f92dd542b65bc910caaf190b7c623aa5158c86a.tar.gz
tqt3-0f92dd542b65bc910caaf190b7c623aa5158c86a.zip
Fix native TQt3 accidental conversion to tquit
Diffstat (limited to 'doc/man/man3')
-rw-r--r--doc/man/man3/qaccel.3qt6
-rw-r--r--doc/man/man3/qapplication.3qt32
-rw-r--r--doc/man/man3/qcdestyle.3qt2
-rw-r--r--doc/man/man3/qcloseevent.3qt2
-rw-r--r--doc/man/man3/qcolorgroup.3qt2
-rw-r--r--doc/man/man3/qdialog.3qt2
-rw-r--r--doc/man/man3/qeventloop.3qt4
-rw-r--r--doc/man/man3/qfont.3qt2
-rw-r--r--doc/man/man3/qglcontext.3qt4
-rw-r--r--doc/man/man3/qhebrewcodec.3qt2
-rw-r--r--doc/man/man3/qlistbox.3qt6
-rw-r--r--doc/man/man3/qmenubar.3qt4
-rw-r--r--doc/man/man3/qmenudata.3qt4
-rw-r--r--doc/man/man3/qnetworkprotocol.3qt2
-rw-r--r--doc/man/man3/qobject.3qt2
-rw-r--r--doc/man/man3/qpopupmenu.3qt4
-rw-r--r--doc/man/man3/qptrqueue.3qt2
-rw-r--r--doc/man/man3/qscrollview.3qt4
-rw-r--r--doc/man/man3/qsessionmanager.3qt2
-rw-r--r--doc/man/man3/qsocket.3qt2
-rw-r--r--doc/man/man3/qsocketdevice.3qt2
-rw-r--r--doc/man/man3/qtimer.3qt2
-rw-r--r--doc/man/man3/qtooltip.3qt6
-rw-r--r--doc/man/man3/qwidget.3qt6
-rw-r--r--doc/man/man3/qxmlsimplereader.3qt2
25 files changed, 54 insertions, 54 deletions
diff --git a/doc/man/man3/qaccel.3qt b/doc/man/man3/qaccel.3qt
index 07e8f3ee8..9c5e23e5f 100644
--- a/doc/man/man3/qaccel.3qt
+++ b/doc/man/man3/qaccel.3qt
@@ -176,7 +176,7 @@ Connects the accelerator item \fIid\fR to the slot \fImember\fR of \fIreceiver\f
.PP
.nf
.br
- a->connectItem( 201, mainView, SLOT(tquit()) );
+ a->connectItem( 201, mainView, SLOT(quit()) );
.br
.fi
.PP
@@ -212,9 +212,9 @@ If \fIid\fR is negative, then the item will be assigned a unique negative identi
.br
a->insertItem( CTRL + Key_P, 200 ); // Ctrl+P, e.g. to print document
.br
- a->insertItem( ALT + Key_X, 201 ); // Alt+X, e.g. to tquit
+ a->insertItem( ALT + Key_X, 201 ); // Alt+X, e.g. to quit
.br
- a->insertItem( UNICODE_ACCEL + 'q', 202 ); // Unicode 'q', e.g. to tquit
+ a->insertItem( UNICODE_ACCEL + 'q', 202 ); // Unicode 'q', e.g. to quit
.br
a->insertItem( Key_D ); // gets a unique negative id < -1
.br
diff --git a/doc/man/man3/qapplication.3qt b/doc/man/man3/qapplication.3qt
index d76b7561a..88db7b847 100644
--- a/doc/man/man3/qapplication.3qt
+++ b/doc/man/man3/qapplication.3qt
@@ -466,7 +466,7 @@ Since it also deals with common command line arguments, it is usually a good ide
.PP
<center>.nf
.TS
-l - l. Groups of functions System settings desktopSettingsAware(), setDesktopSettingsAware(), cursorFlashTime(), setCursorFlashTime(), doubleClickInterval(), setDoubleClickInterval(), wheelScrollLines(), setWheelScrollLines(), palette(), setPalette(), font(), setFont(), fontMetrics(). Event handling exec(), processEvents(), enter_loop(), exit_loop(), exit(), tquit(). sendEvent(), postEvent(), sendPostedEvents(), removePostedEvents(), hasPendingEvents(), notify(), macEventFilter(), qwsEventFilter(), x11EventFilter(), x11ProcessEvent(), winEventFilter(). GUI Styles style(), setStyle(), polish(). Color usage colorSpec(), setColorSpec(), qwsSetCustomColors(). Text handling installTranslator(), removeTranslator() translate(). Widgets mainWidget(), setMainWidget(), allWidgets(), topLevelWidgets(), desktop(), activePopupWidget(), activeModalWidget(), clipboard(), focusWidget(), winFocus(), activeWindow(), widgetAt(). Advanced cursor handling hasGlobalMouseTracking(), setGlobalMouseTracking(), overrideCursor(), setOverrideCursor(), restoreOverrideCursor(). X Window System synchronization flushX(), syncX(). Session management isSessionRestored(), sessionId(), commitData(), saveState(). Threading lock(), unlock(), locked(), tryLock(), wakeUpGuiThread() Miscellaneous
+l - l. Groups of functions System settings desktopSettingsAware(), setDesktopSettingsAware(), cursorFlashTime(), setCursorFlashTime(), doubleClickInterval(), setDoubleClickInterval(), wheelScrollLines(), setWheelScrollLines(), palette(), setPalette(), font(), setFont(), fontMetrics(). Event handling exec(), processEvents(), enter_loop(), exit_loop(), exit(), quit(). sendEvent(), postEvent(), sendPostedEvents(), removePostedEvents(), hasPendingEvents(), notify(), macEventFilter(), qwsEventFilter(), x11EventFilter(), x11ProcessEvent(), winEventFilter(). GUI Styles style(), setStyle(), polish(). Color usage colorSpec(), setColorSpec(), qwsSetCustomColors(). Text handling installTranslator(), removeTranslator() translate(). Widgets mainWidget(), setMainWidget(), allWidgets(), topLevelWidgets(), desktop(), activePopupWidget(), activeModalWidget(), clipboard(), focusWidget(), winFocus(), activeWindow(), widgetAt(). Advanced cursor handling hasGlobalMouseTracking(), setGlobalMouseTracking(), overrideCursor(), setOverrideCursor(), restoreOverrideCursor(). X Window System synchronization flushX(), syncX(). Session management isSessionRestored(), sessionId(), commitData(), saveState(). Threading lock(), unlock(), locked(), tryLock(), wakeUpGuiThread() Miscellaneous
.TE
.fi
</center>
@@ -629,11 +629,11 @@ This is useful for inclusion in the Help menu of an application. See the example
.PP
This function is a convenience slot for QMessageBox::aboutQt().
.SH "void QApplication::aboutToQuit ()\fC [signal]\fR"
-This signal is emitted when the application is about to tquit the main event loop, e.g. when the event loop level drops to zero. This may happen either after a call to tquit() from inside the application or when the users shuts down the entire desktop session.
+This signal is emitted when the application is about to quit the main event loop, e.g. when the event loop level drops to zero. This may happen either after a call to quit() from inside the application or when the users shuts down the entire desktop session.
.PP
The signal is particularly useful if your application has to do some last-second cleanup. Note that no user interaction is possible in this state.
.PP
-See also tquit().
+See also quit().
.SH "QWidget * QApplication::activeModalWidget ()\fC [static]\fR"
Returns the active modal widget.
.PP
@@ -795,15 +795,15 @@ This function is particularly useful for applications with many top-level window
file->insertItem( "&Quit", qApp, SLOT(closeAllWindows()), CTRL+Key_Q );
.br
.br
- // when the last window is closed, the application should tquit
+ // when the last window is closed, the application should quit
.br
- connect( qApp, SIGNAL( lastWindowClosed() ), qApp, SLOT( tquit() ) );
+ connect( qApp, SIGNAL( lastWindowClosed() ), qApp, SLOT( quit() ) );
.br
.fi
.PP
The windows are closed in random order, until one window does not accept the close event.
.PP
-See also QWidget::close(), QWidget::closeEvent(), lastWindowClosed(), tquit(), topLevelWidgets(), and QWidget::isTopLevel.
+See also QWidget::close(), QWidget::closeEvent(), lastWindowClosed(), quit(), topLevelWidgets(), and QWidget::isTopLevel.
.PP
Examples:
.)l action/application.cpp, application/application.cpp, helpviewer/helpwindow.cpp, mdi/application.cpp, and qwerty/qwerty.cpp.
@@ -883,7 +883,7 @@ See also QEventLoop.
.PP
Example: distributor/distributor.ui.h.
.SH "int QApplication::exec ()"
-Enters the main event loop and waits until exit() is called or the main widget is destroyed, and returns the value that was set to exit() (which is 0 if exit() is called via tquit()).
+Enters the main event loop and waits until exit() is called or the main widget is destroyed, and returns the value that was set to exit() (which is 0 if exit() is called via quit()).
.PP
It is necessary to call this function to start event handling. The main event loop receives events from the window system and dispatches these to the application widgets.
.PP
@@ -891,7 +891,7 @@ Generally speaking, no user interaction can take place before calling exec(). As
.PP
To make your application perform idle processing, i.e. executing a special function whenever there are no pending events, use a QTimer with 0 timeout. More advanced idle processing schemes can be achieved using processEvents().
.PP
-See also tquit(), exit(), processEvents(), and setMainWidget().
+See also quit(), exit(), processEvents(), and setMainWidget().
.PP
Examples:
.)l helpsystem/main.cpp, life/main.cpp, network/archivesearch/main.cpp, network/ftpclient/main.cpp, opengl/main.cpp, t1/main.cpp, and t4/main.cpp.
@@ -904,7 +904,7 @@ By convention, a \fIretcode\fR of 0 means success, and any non-zero value indica
.PP
Note that unlike the C library function of the same name, this function \fIdoes\fR return to the caller -- it is event processing that stops.
.PP
-See also tquit() and exec().
+See also quit() and exec().
.PP
Examples:
.)l chart/chartform.cpp, extension/mainform.ui.h, and picture/picture.cpp.
@@ -982,7 +982,7 @@ See also sessionId(), commitData(), and saveState().
.SH "void QApplication::lastWindowClosed ()\fC [signal]\fR"
This signal is emitted when the user has closed the last top level window.
.PP
-The signal is very useful when your application has many top level widgets but no main widget. You can then connect it to the tquit() slot.
+The signal is very useful when your application has many top level widgets but no main widget. You can then connect it to the quit() slot.
.PP
For convenience, this signal is \fInot\fR emitted for transient top level widgets such as popup menus and dialogs.
.PP
@@ -1120,18 +1120,18 @@ This function is useful for adapting Qt to situations where the event processing
Using this function in new applications may be an indication of design problems.
.PP
See also processEvents(), exec(), and QTimer.
-.SH "void QApplication::tquit ()\fC [slot]\fR"
+.SH "void QApplication::quit ()\fC [slot]\fR"
Tells the application to exit with return code 0 (success). Equivalent to calling QApplication::exit( 0 ).
.PP
-It's common to connect the lastWindowClosed() signal to tquit(), and you also often connect e.g. QButton::clicked() or signals in QAction, QPopupMenu or QMenuBar to it.
+It's common to connect the lastWindowClosed() signal to quit(), and you also often connect e.g. QButton::clicked() or signals in QAction, QPopupMenu or QMenuBar to it.
.PP
Example:
.PP
.nf
.br
- QPushButton *tquitButton = new QPushButton( "Quit" );
+ QPushButton *quitButton = new QPushButton( "Quit" );
.br
- connect( tquitButton, SIGNAL(clicked()), qApp, SLOT(tquit()) );
+ connect( quitButton, SIGNAL(clicked()), qApp, SLOT(quit()) );
.br
.fi
.PP
@@ -1404,11 +1404,11 @@ Sets the application's main widget to \fImainWidget\fR.
.PP
In most respects the main widget is like any other widget, except that if it is closed, the application exits. Note that QApplication does \fInot\fR take ownership of the \fImainWidget\fR, so if you create your main widget on the heap you must delete it yourself.
.PP
-You need not have a main widget; connecting lastWindowClosed() to tquit() is an alternative.
+You need not have a main widget; connecting lastWindowClosed() to quit() is an alternative.
.PP
For X11, this function also resizes and moves the main widget according to the \fI-geometry\fR command-line option, so you should set the default geometry (using QWidget::setGeometry()) before calling setMainWidget().
.PP
-See also mainWidget(), exec(), and tquit().
+See also mainWidget(), exec(), and quit().
.PP
Examples:
.)l chart/main.cpp, helpsystem/main.cpp, life/main.cpp, network/ftpclient/main.cpp, opengl/main.cpp, t1/main.cpp, and t4/main.cpp.
diff --git a/doc/man/man3/qcdestyle.3qt b/doc/man/man3/qcdestyle.3qt
index 5835be2b3..9f5b92f8a 100644
--- a/doc/man/man3/qcdestyle.3qt
+++ b/doc/man/man3/qcdestyle.3qt
@@ -25,7 +25,7 @@ Inherits QMotifStyle.
.SH DESCRIPTION
The QCDEStyle class provides a CDE look and feel.
.PP
-This style provides a slightly improved Motif look similar to some versions of the Common Desktop Environment (CDE). The main differences are thinner frames and more modern radio buttons and checkboxes. Together with a dark background and a bright text/foreground color, the style looks tquite attractive (at least for Motif fans).
+This style provides a slightly improved Motif look similar to some versions of the Common Desktop Environment (CDE). The main differences are thinner frames and more modern radio buttons and checkboxes. Together with a dark background and a bright text/foreground color, the style looks quite attractive (at least for Motif fans).
.PP
Note that the functions provided by QCDEStyle are reimplementations of QStyle functions; see QStyle for their documentation.
.PP
diff --git a/doc/man/man3/qcloseevent.3qt b/doc/man/man3/qcloseevent.3qt
index 03ed11727..1032d13a3 100644
--- a/doc/man/man3/qcloseevent.3qt
+++ b/doc/man/man3/qcloseevent.3qt
@@ -49,7 +49,7 @@ If the last top-level window is closed, the QApplication::lastWindowClosed() sig
.PP
The isAccepted() function returns TRUE if the event's receiver has agreed to close the widget; call accept() to agree to close the widget and call ignore() if the receiver of this event does not want the widget to be closed.
.PP
-See also QWidget::close(), QWidget::hide(), QObject::destroyed(), QApplication::setMainWidget(), QApplication::lastWindowClosed(), QApplication::exec(), QApplication::tquit(), and Event Classes.
+See also QWidget::close(), QWidget::hide(), QObject::destroyed(), QApplication::setMainWidget(), QApplication::lastWindowClosed(), QApplication::exec(), QApplication::quit(), and Event Classes.
.SH MEMBER FUNCTION DOCUMENTATION
.SH "QCloseEvent::QCloseEvent ()"
Constructs a close event object with the accept parameter flag set to FALSE.
diff --git a/doc/man/man3/qcolorgroup.3qt b/doc/man/man3/qcolorgroup.3qt
index 0bde55063..de2e82f85 100644
--- a/doc/man/man3/qcolorgroup.3qt
+++ b/doc/man/man3/qcolorgroup.3qt
@@ -185,7 +185,7 @@ Finally, there is a special role for text that needs to be drawn where Text or F
.TP
\fCQColorGroup::NColorRoles\fR - Internal.
.PP
-Note that text colors can be used for things other than just words; text colors are \fIusually\fR used for text, but it's tquite common to use the text color roles for lines, icons, etc.
+Note that text colors can be used for things other than just words; text colors are \fIusually\fR used for text, but it's quite common to use the text color roles for lines, icons, etc.
.PP
This image shows most of the color roles in use: <center>
.ce 1
diff --git a/doc/man/man3/qdialog.3qt b/doc/man/man3/qdialog.3qt
index 31f3911bd..7d23207f6 100644
--- a/doc/man/man3/qdialog.3qt
+++ b/doc/man/man3/qdialog.3qt
@@ -213,7 +213,7 @@ Closes the dialog and sets its result code to \fIr\fR. If this dialog is shown w
.PP
As with QWidget::close(), done() deletes the dialog if the WDestructiveClose flag is set. If the dialog is the application's main widget, the application terminates. If the dialog is the last window closed, the QApplication::lastWindowClosed() signal is emitted.
.PP
-See also accept(), reject(), QApplication::mainWidget(), and QApplication::tquit().
+See also accept(), reject(), QApplication::mainWidget(), and QApplication::quit().
.SH "int QDialog::exec ()\fC [slot]\fR"
Shows the dialog as a modal dialog, blocking until the user closes it. The function returns a DialogCode result.
.PP
diff --git a/doc/man/man3/qeventloop.3qt b/doc/man/man3/qeventloop.3qt
index a72100022..cf7a0fee4 100644
--- a/doc/man/man3/qeventloop.3qt
+++ b/doc/man/man3/qeventloop.3qt
@@ -147,7 +147,7 @@ Generally speaking, no user interaction can take place before calling exec(). As
.PP
To make your application perform idle processing, i.e. executing a special function whenever there are no pending events, use a QTimer with 0 timeout. More advanced idle processing schemes can be achieved using processEvents().
.PP
-See also QApplication::tquit(), exit(), and processEvents().
+See also QApplication::quit(), exit(), and processEvents().
.SH "void QEventLoop::exit ( int retcode = 0 )\fC [virtual]\fR"
Tells the event loop to exit with a return code.
.PP
@@ -157,7 +157,7 @@ By convention, a \fIretcode\fR of 0 means success, and any non-zero value indica
.PP
Note that unlike the C library function of the same name, this function \fIdoes\fR return to the caller -- it is event processing that stops.
.PP
-See also QApplication::tquit() and exec().
+See also QApplication::quit() and exec().
.SH "void QEventLoop::exitLoop ()\fC [virtual]\fR"
This function exits from a recursive call to the main event loop. Do not call it unless you really know what you are doing.
.SH "bool QEventLoop::hasPendingEvents () const\fC [virtual]\fR"
diff --git a/doc/man/man3/qfont.3qt b/doc/man/man3/qfont.3qt
index 962ba6128..d3c413ff6 100644
--- a/doc/man/man3/qfont.3qt
+++ b/doc/man/man3/qfont.3qt
@@ -392,7 +392,7 @@ South and Southeast Asian scripts (left to right with few historical exceptions)
.TP
\fCQFont::Thai\fR - is used to write Thai and other Southeast Asian languages.
.TP
-\fCQFont::Lao\fR - is a language and script tquite similar to Thai.
+\fCQFont::Lao\fR - is a language and script quite similar to Thai.
.TP
\fCQFont::Tibetan\fR - is the script used to write Tibetan in several countries like Tibet, the bordering Indian regions and Nepal. It is also used in the Buddist philosophy and liturgy of the Mongolian cultural area.
.TP
diff --git a/doc/man/man3/qglcontext.3qt b/doc/man/man3/qglcontext.3qt
index d90d57f61..13ff2fbcd 100644
--- a/doc/man/man3/qglcontext.3qt
+++ b/doc/man/man3/qglcontext.3qt
@@ -131,7 +131,7 @@ On Windows, it calls the virtual function choosePixelFormat(), which finds a mat
.SH "void * QGLContext::chooseMacVisual ( GDHandle device )\fC [virtual protected]\fR"
\fBMac only\fR: This virtual function tries to find a visual that matches the format using the given \fIdevice\fR handle, reducing the demands if the original request cannot be met.
.PP
-The algorithm for reducing the demands of the format is tquite simple-minded, so override this method in your subclass if your application has specific retquirements on visual selection.
+The algorithm for reducing the demands of the format is quite simple-minded, so override this method in your subclass if your application has specific retquirements on visual selection.
.PP
See also chooseContext().
.SH "int QGLContext::choosePixelFormat ( void * dummyPfd, HDC pdc )\fC [virtual protected]\fR"
@@ -143,7 +143,7 @@ See also chooseContext().
.SH "void * QGLContext::chooseVisual ()\fC [virtual protected]\fR"
\fBX11 only\fR: This virtual function tries to find a visual that matches the format, reducing the demands if the original request cannot be met.
.PP
-The algorithm for reducing the demands of the format is tquite simple-minded, so override this method in your subclass if your application has spcific retquirements on visual selection.
+The algorithm for reducing the demands of the format is quite simple-minded, so override this method in your subclass if your application has spcific retquirements on visual selection.
.PP
See also chooseContext().
.SH "bool QGLContext::create ( const QGLContext * shareContext = 0 )\fC [virtual]\fR"
diff --git a/doc/man/man3/qhebrewcodec.3qt b/doc/man/man3/qhebrewcodec.3qt
index 63a39d67d..e07d93ef3 100644
--- a/doc/man/man3/qhebrewcodec.3qt
+++ b/doc/man/man3/qhebrewcodec.3qt
@@ -33,7 +33,7 @@ In contrast to this, Unicode defines characters to be in logical order (the orde
.PP
Transformation from Unicode to visual Hebrew (8859-8) is done using the bidi algorithm in Qt, and will produce correct results, so long as the codec is given the text a whole paragraph at a time. Places where newlines are supposed to go can be indicated by a newline character ('\\n'). Note that these newline characters change the reordering behaviour of the algorithm, since the bidi reordering only takes place within one line of text, whereas line breaks are determined in visual order.
.PP
-Visually ordered Hebrew is still used tquite often in some places, mainly in email communication (since most email programs still don't understand logically ordered Hebrew) and on web pages. The use on web pages is rapidly decreasing, due to the availability of browsers that correctly support logically ordered Hebrew.
+Visually ordered Hebrew is still used quite often in some places, mainly in email communication (since most email programs still don't understand logically ordered Hebrew) and on web pages. The use on web pages is rapidly decreasing, due to the availability of browsers that correctly support logically ordered Hebrew.
.PP
This codec has the name "iso8859-8". If you don't want any bidi reordering to happen during conversion, use the "iso8859-8-i" codec, which assumes logical order for the 8-bit string.
.PP
diff --git a/doc/man/man3/qlistbox.3qt b/doc/man/man3/qlistbox.3qt
index 9d842ca17..7608d6270 100644
--- a/doc/man/man3/qlistbox.3qt
+++ b/doc/man/man3/qlistbox.3qt
@@ -441,7 +441,7 @@ If the user does not select anything, no signals are emitted and currentItem() r
.PP
A list box has WheelFocus as a default focusPolicy(), i.e. it can get keyboard focus by tabbing, clicking and through the use of the mouse wheel.
.PP
-New items can be inserted using insertItem(), insertStrList() or insertStringList(). inSort() is obsolete because this method is tquite inefficient. It's preferable to insert the items normally and call sort() afterwards, or to insert a sorted QStringList().
+New items can be inserted using insertItem(), insertStrList() or insertStringList(). inSort() is obsolete because this method is quite inefficient. It's preferable to insert the items normally and call sort() afterwards, or to insert a sorted QStringList().
.PP
By default, vertical and horizontal scroll bars are added and removed as necessary. setHScrollBarMode() and setVScrollBarMode() can be used to change this policy.
.PP
@@ -634,7 +634,7 @@ See also currentChanged(), selected(), currentItem, and selectionChanged().
.SH "int QListBox::inSort ( const QListBoxItem * lbi )"
\fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code.
.PP
-Using this method is tquite inefficient. We suggest to use insertItem() for inserting and sort() afterwards.
+Using this method is quite inefficient. We suggest to use insertItem() for inserting and sort() afterwards.
.PP
Inserts \fIlbi\fR at its sorted position in the list box and returns the position.
.PP
@@ -646,7 +646,7 @@ See also insertItem() and sort().
.PP
This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
.PP
-Using this method is tquite inefficient. We suggest to use insertItem() for inserting and sort() afterwards.
+Using this method is quite inefficient. We suggest to use insertItem() for inserting and sort() afterwards.
.PP
Inserts a new item of \fItext\fR at its sorted position in the list box and returns the position.
.PP
diff --git a/doc/man/man3/qmenubar.3qt b/doc/man/man3/qmenubar.3qt
index e1308a6ba..f31b2d3ef 100644
--- a/doc/man/man3/qmenubar.3qt
+++ b/doc/man/man3/qmenubar.3qt
@@ -218,7 +218,7 @@ Qt/Mac also provides a menubar merging feature to make QMenuBar conform more clo
.PP
<center>.nf
.TS
-l - l. String matches Placement Notes about.* Application Menu | About If this entry is not found no About item will appear in the Application Menu config, options, setup, settings or preferences Application Menu | Preferences If this entry is not found the Settings item will be disabled tquit or exit Application Menu | Quit If this entry is not found a default Quit item will be created to call
+l - l. String matches Placement Notes about.* Application Menu | About If this entry is not found no About item will appear in the Application Menu config, options, setup, settings or preferences Application Menu | Preferences If this entry is not found the Settings item will be disabled quit or exit Application Menu | Quit If this entry is not found a default Quit item will be created to call
.TE
.fi
</center>
@@ -282,7 +282,7 @@ A menu item is usually either a text string or a pixmap, both with an optional i
.PP
Some insertItem() members take a popup menu as an additional argument. Use this to insert submenus into existing menus or pulldown menus into a menu bar.
.PP
-The number of insert functions may look confusing, but they are actually tquite simple to use.
+The number of insert functions may look confusing, but they are actually quite simple to use.
.PP
This default version inserts a menu item with the text \fItext\fR, the accelerator key \fIaccel\fR, an id and an optional index and connects it to the slot \fImember\fR in the object \fIreceiver\fR.
.PP
diff --git a/doc/man/man3/qmenudata.3qt b/doc/man/man3/qmenudata.3qt
index 9199b1b06..306f5d4fb 100644
--- a/doc/man/man3/qmenudata.3qt
+++ b/doc/man/man3/qmenudata.3qt
@@ -322,7 +322,7 @@ A menu item is usually either a text string or a pixmap, both with an optional i
.PP
Some insertItem() members take a popup menu as an additional argument. Use this to insert submenus into existing menus or pulldown menus into a menu bar.
.PP
-The number of insert functions may look confusing, but they are actually tquite simple to use.
+The number of insert functions may look confusing, but they are actually quite simple to use.
.PP
This default version inserts a menu item with the text \fItext\fR, the accelerator key \fIaccel\fR, an id and an optional index and connects it to the slot \fImember\fR in the object \fIreceiver\fR.
.PP
@@ -607,7 +607,7 @@ Example:
.br
fileMenu->insertItem( "Quit", 69 ); // add "Quit" item
.br
- fileMenu->setAccel( CTRL + ALT + Key_Delete, 69 ); // add Alt+Del to tquit
+ fileMenu->setAccel( CTRL + ALT + Key_Delete, 69 ); // add Alt+Del to quit
.br
mainMenu->insertItem( "File", fileMenu ); // add the file menu
.br
diff --git a/doc/man/man3/qnetworkprotocol.3qt b/doc/man/man3/qnetworkprotocol.3qt
index 6760cc76f..3d1a15197 100644
--- a/doc/man/man3/qnetworkprotocol.3qt
+++ b/doc/man/man3/qnetworkprotocol.3qt
@@ -226,7 +226,7 @@ Returns TRUE if auto-deleting is enabled; otherwise returns FALSE.
.PP
See also QNetworkProtocol::setAutoDelete().
.SH "bool QNetworkProtocol::checkConnection ( QNetworkOperation * op )\fC [virtual protected]\fR"
-For processing operations the network protocol base class calls this method tquite often. This should be reimplemented by new network protocols. It should return TRUE if the connection is OK (open); otherwise it should return FALSE. If the connection is not open the protocol should open it.
+For processing operations the network protocol base class calls this method quite often. This should be reimplemented by new network protocols. It should return TRUE if the connection is OK (open); otherwise it should return FALSE. If the connection is not open the protocol should open it.
.PP
If the connection can't be opened (e.g. because you already tried but the host couldn't be found), set the state of \fIop\fR to QNetworkProtocol::StFailed and emit the finished() signal with this QNetworkOperation as argument.
.PP
diff --git a/doc/man/man3/qobject.3qt b/doc/man/man3/qobject.3qt
index 8dcb7c829..e1d365474 100644
--- a/doc/man/man3/qobject.3qt
+++ b/doc/man/man3/qobject.3qt
@@ -779,7 +779,7 @@ Searches the children and optionally grandchildren of this object, and returns a
.PP
If \fIregexpMatch\fR is TRUE (the default), \fIobjName\fR is a regular expression that the objects's names must match. The syntax is that of a QRegExp. If \fIregexpMatch\fR is FALSE, \fIobjName\fR is a string and object names must match it exactly.
.PP
-Note that \fIinheritsClass\fR uses single inheritance from QObject, the way inherits() does. According to inherits(), QMenuBar inherits QWidget but not QMenuData. This does not tquite match reality, but is the best that can be done on the wide variety of compilers Qt supports.
+Note that \fIinheritsClass\fR uses single inheritance from QObject, the way inherits() does. According to inherits(), QMenuBar inherits QWidget but not QMenuData. This does not quite match reality, but is the best that can be done on the wide variety of compilers Qt supports.
.PP
Finally, if \fIrecursiveSearch\fR is TRUE (the default), queryList() searches \fIn\fRth-generation as well as first-generation children.
.PP
diff --git a/doc/man/man3/qpopupmenu.3qt b/doc/man/man3/qpopupmenu.3qt
index a20cd7c5c..10d3fff5f 100644
--- a/doc/man/man3/qpopupmenu.3qt
+++ b/doc/man/man3/qpopupmenu.3qt
@@ -410,7 +410,7 @@ A menu item is usually either a text string or a pixmap, both with an optional i
.PP
Some insertItem() members take a popup menu as an additional argument. Use this to insert submenus into existing menus or pulldown menus into a menu bar.
.PP
-The number of insert functions may look confusing, but they are actually tquite simple to use.
+The number of insert functions may look confusing, but they are actually quite simple to use.
.PP
This default version inserts a menu item with the text \fItext\fR, the accelerator key \fIaccel\fR, an id and an optional index and connects it to the slot \fImember\fR in the object \fIreceiver\fR.
.PP
@@ -703,7 +703,7 @@ Example:
.br
fileMenu->insertItem( "Quit", 69 ); // add "Quit" item
.br
- fileMenu->setAccel( CTRL + ALT + Key_Delete, 69 ); // add Alt+Del to tquit
+ fileMenu->setAccel( CTRL + ALT + Key_Delete, 69 ); // add Alt+Del to quit
.br
mainMenu->insertItem( "File", fileMenu ); // add the file menu
.br
diff --git a/doc/man/man3/qptrqueue.3qt b/doc/man/man3/qptrqueue.3qt
index 66fc1a6ac..592506e03 100644
--- a/doc/man/man3/qptrqueue.3qt
+++ b/doc/man/man3/qptrqueue.3qt
@@ -148,7 +148,7 @@ See also head(), isEmpty(), and dequeue().
.SH "void QPtrQueue::setAutoDelete ( bool enable )"
Sets the queue to auto-delete its contents if \fIenable\fR is TRUE and not to delete them if \fIenable\fR is FALSE.
.PP
-If auto-deleting is turned on, all the items in a queue are deleted when the queue itself is deleted. This can be tquite convenient if the queue has the only pointer to the items.
+If auto-deleting is turned on, all the items in a queue are deleted when the queue itself is deleted. This can be quite convenient if the queue has the only pointer to the items.
.PP
The default setting is FALSE, for safety. If you turn it on, be careful about copying the queue: you might find yourself with two queues deleting the same items.
.PP
diff --git a/doc/man/man3/qscrollview.3qt b/doc/man/man3/qscrollview.3qt
index 611a870ed..617341f1a 100644
--- a/doc/man/man3/qscrollview.3qt
+++ b/doc/man/man3/qscrollview.3qt
@@ -309,7 +309,7 @@ Inherited by QCanvasView, QTable, QGridView, QIconView, QListBox, QListView, and
.SH DESCRIPTION
The QScrollView widget provides a scrolling area with on-demand scroll bars.
.PP
-The QScrollView is a large canvas - potentially larger than the coordinate system normally supported by the underlying window system. This is important because it is tquite easy to go beyond these limitations (e.g. many web pages are more than 32000 pixels high). Additionally, the QScrollView can have QWidgets positioned on it that scroll around with the drawn content. These sub-widgets can also have positions outside the normal coordinate range (but they are still limited in size).
+The QScrollView is a large canvas - potentially larger than the coordinate system normally supported by the underlying window system. This is important because it is quite easy to go beyond these limitations (e.g. many web pages are more than 32000 pixels high). Additionally, the QScrollView can have QWidgets positioned on it that scroll around with the drawn content. These sub-widgets can also have positions outside the normal coordinate range (but they are still limited in size).
.PP
To provide content for the widget, inherit from QScrollView, reimplement drawContents() and use resizeContents() to set the size of the viewed area. Use addChild() and moveChild() to position widgets on the view.
.PP
@@ -757,7 +757,7 @@ Sets the resize policy. See the "resizePolicy" property for details.
.SH "void QScrollView::setStaticBackground ( bool y )"
Sets the scrollview to have a static background if \fIy\fR is TRUE, or a scrolling background if \fIy\fR is FALSE. By default, the background is scrolling.
.PP
-Be aware that this mode is tquite slow, as a full repaint of the visible area has to be triggered on every contents move.
+Be aware that this mode is quite slow, as a full repaint of the visible area has to be triggered on every contents move.
.PP
See also hasStaticBackground().
.SH "void QScrollView::setVBarGeometry ( QScrollBar & vbar, int x, int y, int w, int h )\fC [virtual protected]\fR"
diff --git a/doc/man/man3/qsessionmanager.3qt b/doc/man/man3/qsessionmanager.3qt
index db170b1f4..5a7eb0e79 100644
--- a/doc/man/man3/qsessionmanager.3qt
+++ b/doc/man/man3/qsessionmanager.3qt
@@ -90,7 +90,7 @@ This enum type defines the circumstances under which this application wants to b
.TP
\fCQSessionManager::RestartIfRunning\fR - if the application is still running when the session is shut down, it wants to be restarted at the start of the next session.
.TP
-\fCQSessionManager::RestartAnyway\fR - the application wants to be started at the start of the next session, no matter what. (This is useful for utilities that run just after startup and then tquit.)
+\fCQSessionManager::RestartAnyway\fR - the application wants to be started at the start of the next session, no matter what. (This is useful for utilities that run just after startup and then quit.)
.TP
\fCQSessionManager::RestartImmediately\fR - the application wants to be started immediately whenever it is not running.
.TP
diff --git a/doc/man/man3/qsocket.3qt b/doc/man/man3/qsocket.3qt
index 7dd6273bd..650721783 100644
--- a/doc/man/man3/qsocket.3qt
+++ b/doc/man/man3/qsocket.3qt
@@ -165,7 +165,7 @@ The signals error(), connected(), readyRead() and connectionClosed() inform you
.PP
There are several access functions for the socket: state() returns whether the object is idle, is doing a DNS lookup, is connecting, has an operational connection, etc. address() and port() return the IP address and port used for the connection. The peerAddress() and peerPort() functions return the IP address and port used by the peer, and peerName() returns the name of the peer (normally the name that was passed to connectToHost()). socketDevice() returns a pointer to the QSocketDevice used for this socket.
.PP
-QSocket inherits QIODevice, and reimplements some functions. In general, you can treat it as a QIODevice for writing, and mostly also for reading. The match isn't perfect, since the QIODevice API is designed for devices that are controlled by the same machine, and an asynchronous peer-to-peer network connection isn't tquite like that. For example, there is nothing that matches QIODevice::size() exactly. The documentation for open(), close(), flush(), size(), at(), atEnd(), readBlock(), writeBlock(), getch(), putch(), ungetch() and readLine() describes the differences in detail.
+QSocket inherits QIODevice, and reimplements some functions. In general, you can treat it as a QIODevice for writing, and mostly also for reading. The match isn't perfect, since the QIODevice API is designed for devices that are controlled by the same machine, and an asynchronous peer-to-peer network connection isn't quite like that. For example, there is nothing that matches QIODevice::size() exactly. The documentation for open(), close(), flush(), size(), at(), atEnd(), readBlock(), writeBlock(), getch(), putch(), ungetch() and readLine() describes the differences in detail.
.PP
\fBWarning:\fR QSocket is not suitable for use in threads. If you need to uses sockets in threads use the lower-level QSocketDevice class.
.PP
diff --git a/doc/man/man3/qsocketdevice.3qt b/doc/man/man3/qsocketdevice.3qt
index 7814ce3ac..d18322eed 100644
--- a/doc/man/man3/qsocketdevice.3qt
+++ b/doc/man/man3/qsocketdevice.3qt
@@ -244,7 +244,7 @@ Returns TRUE if this is a valid socket; otherwise returns FALSE.
.PP
See also socket().
.SH "bool QSocketDevice::listen ( int backlog )\fC [virtual]\fR"
-Specifies how many pending connections a server socket can have. Returns TRUE if the operation was successful; otherwise returns FALSE. A \fIbacklog\fR value of 50 is tquite common.
+Specifies how many pending connections a server socket can have. Returns TRUE if the operation was successful; otherwise returns FALSE. A \fIbacklog\fR value of 50 is quite common.
.PP
The listen() call only applies to sockets where type() is Stream, i.e. not to Datagram sockets. listen() must not be called before bind() or after accept().
.PP
diff --git a/doc/man/man3/qtimer.3qt b/doc/man/man3/qtimer.3qt
index 50cb9a851..b4b492bca 100644
--- a/doc/man/man3/qtimer.3qt
+++ b/doc/man/man3/qtimer.3qt
@@ -130,7 +130,7 @@ Example:
.br
QApplication a( argc, argv );
.br
- QTimer::singleShot( 10*60*1000, &a, SLOT(tquit()) );
+ QTimer::singleShot( 10*60*1000, &a, SLOT(quit()) );
.br
... // create and show your widgets
.br
diff --git a/doc/man/man3/qtooltip.3qt b/doc/man/man3/qtooltip.3qt
index 2511f9ed4..30be67b73 100644
--- a/doc/man/man3/qtooltip.3qt
+++ b/doc/man/man3/qtooltip.3qt
@@ -125,7 +125,7 @@ To add a tip to a widget, call the \fIstatic\fR function QToolTip::add() with th
.PP
.nf
.br
- QToolTip::add( tquitButton, "Leave the application" );
+ QToolTip::add( quitButton, "Leave the application" );
.br
.fi
.PP
@@ -133,7 +133,7 @@ This is the simplest and most common use of QToolTip. The tip will be deleted au
.PP
.nf
.br
- QToolTip::remove( tquitButton );
+ QToolTip::remove( quitButton );
.br
.fi
.PP
@@ -141,7 +141,7 @@ You can also display another text (typically in a status bar), courtesy of QTool
.PP
.nf
.br
- QToolTip::add( tquitButton, "Leave the application", grp,
+ QToolTip::add( quitButton, "Leave the application", grp,
.br
"Leave the application, prompting to save if necessary" );
.br
diff --git a/doc/man/man3/qwidget.3qt b/doc/man/man3/qwidget.3qt
index 007f06f2f..2da51743d 100644
--- a/doc/man/man3/qwidget.3qt
+++ b/doc/man/man3/qwidget.3qt
@@ -1028,7 +1028,7 @@ Every widget's constructor accepts two or three standard arguments: <ol type=1>
.IP 1
\fCQWidget *parent = 0\fR is the parent of the new widget. If it is 0 (the default), the new widget will be a top-level window. If not, it will be a child of \fIparent\fR, and be constrained by \fIparent\fR's geometry (unless you specify WType_TopLevel as widget flag).
.IP 2
-\fCconst char *name = 0\fR is the widget name of the new widget. You can access it using name(). The widget name is little used by programmers but is tquite useful with GUI builders such as \fIQt Designer\fR (you can name a widget in \fIQt Designer\fR, and connect() to it using the name in your code). The dumpObjectTree() debugging function also uses it.
+\fCconst char *name = 0\fR is the widget name of the new widget. You can access it using name(). The widget name is little used by programmers but is quite useful with GUI builders such as \fIQt Designer\fR (you can name a widget in \fIQt Designer\fR, and connect() to it using the name in your code). The dumpObjectTree() debugging function also uses it.
.IP 3
\fCWFlags f = 0\fR (where available) sets the widget flags; the default is suitable for almost all widgets, but to get, for example, a top-level widget without a window system frame, you must use special flags.
.PP
@@ -1049,7 +1049,7 @@ mousePressEvent() - called when a mouse button is pressed. There are six mouse-r
mouseReleaseEvent() - called when a mouse button is released. A widget receives mouse release events when it has received the corresponding mouse press event. This means that if the user presses the mouse inside \fIyour\fR widget, then drags the mouse to somewhere else, then releases, \fIyour\fR widget receives the release event. There is one exception: if a popup menu appears while the mouse button is held down, this popup immediately steals the mouse events.
.IP
.TP
-mouseDoubleClickEvent() - not tquite as obvious as it might seem. If the user double-clicks, the widget receives a mouse press event (perhaps a mouse move event or two if they don't hold the mouse tquite steady), a mouse release event and finally this event. It is \fInot possible\fR to distinguish a click from a double click until you've seen whether the second click arrives. (This is one reason why most GUI books recommend that double clicks be an extension of single clicks, rather than trigger a different action.)
+mouseDoubleClickEvent() - not quite as obvious as it might seem. If the user double-clicks, the widget receives a mouse press event (perhaps a mouse move event or two if they don't hold the mouse quite steady), a mouse release event and finally this event. It is \fInot possible\fR to distinguish a click from a double click until you've seen whether the second click arrives. (This is one reason why most GUI books recommend that double clicks be an extension of single clicks, rather than trigger a different action.)
.IP
.PP
If your widget only contains child widgets, you probably do not need to implement any event handlers. If you want to detect a mouse click in a child widget call the child's hasMouse() function inside the parent widget's mousePressEvent().
@@ -1247,7 +1247,7 @@ The QApplication::lastWindowClosed() signal is emitted when the last visible top
.PP
Note that closing the QApplication::mainWidget() terminates the application.
.PP
-See also closeEvent(), QCloseEvent, hide(), QApplication::tquit(), QApplication::setMainWidget(), and QApplication::lastWindowClosed().
+See also closeEvent(), QCloseEvent, hide(), QApplication::quit(), QApplication::setMainWidget(), and QApplication::lastWindowClosed().
.SH "void QWidget::closeEvent ( QCloseEvent * e )\fC [virtual protected]\fR"
This event handler, for event \fIe\fR, can be reimplemented in a subclass to receive widget close events.
.PP
diff --git a/doc/man/man3/qxmlsimplereader.3qt b/doc/man/man3/qxmlsimplereader.3qt
index 2c4f5253e..5b1d6d721 100644
--- a/doc/man/man3/qxmlsimplereader.3qt
+++ b/doc/man/man3/qxmlsimplereader.3qt
@@ -77,7 +77,7 @@ Continues incremental parsing; this function reads the input from the QXmlInputS
.PP
Returns FALSE if a parsing error occurs; otherwise returns TRUE.
.PP
-If the input source returns an empty string for the function QXmlInputSource::data(), then this means that the end of the XML file has been reached; this is tquite important, especially if you want to use the reader to parse more than one XML file.
+If the input source returns an empty string for the function QXmlInputSource::data(), then this means that the end of the XML file has been reached; this is quite important, especially if you want to use the reader to parse more than one XML file.
.PP
The case of the end of the XML file being reached without having finished parsing is not considered to be an error: you can continue parsing at a later stage by calling this function again when there is more data available to parse.
.PP