summaryrefslogtreecommitdiffstats
path: root/doc/html/qwidget.html
diff options
context:
space:
mode:
authorTimothy Pearson <kb9vqf@pearsoncomputing.net>2011-11-14 22:33:41 -0600
committerTimothy Pearson <kb9vqf@pearsoncomputing.net>2011-11-14 22:33:41 -0600
commit0f92dd542b65bc910caaf190b7c623aa5158c86a (patch)
tree120ab7e08fa0ffc354ef58d100f79a33c92aa6e6 /doc/html/qwidget.html
parentd796c9dd933ab96ec83b9a634feedd5d32e1ba3f (diff)
downloadtqt3-0f92dd542b65bc910caaf190b7c623aa5158c86a.tar.gz
tqt3-0f92dd542b65bc910caaf190b7c623aa5158c86a.zip
Fix native TQt3 accidental conversion to tquit
Diffstat (limited to 'doc/html/qwidget.html')
-rw-r--r--doc/html/qwidget.html8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/html/qwidget.html b/doc/html/qwidget.html
index 982c0a19..2d76389b 100644
--- a/doc/html/qwidget.html
+++ b/doc/html/qwidget.html
@@ -569,7 +569,7 @@ If not, it will be a child of <em>parent</em>, and be constrained by <em>parent<
<a href="qt.html#WidgetFlags">widget flag</a>).
<li> <tt>const char *name = 0</tt> is the widget name of the new
widget. You can access it using <a href="qobject.html#name">name</a>(). The widget name is little
-used by programmers but is tquite useful with GUI builders such as
+used by programmers but is quite useful with GUI builders such as
<em>TQt Designer</em> (you can name a widget in <em>TQt Designer</em>, and
<a href="qobject.html#connect">connect</a>() to it using the name in your code). The <a href="qobject.html#dumpObjectTree">dumpObjectTree</a>()
debugging function also uses it.
@@ -606,10 +606,10 @@ somewhere else, then releases, <em>your</em> 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.
-<p> <li> <a href="#mouseDoubleClickEvent">mouseDoubleClickEvent</a>() - not tquite as obvious as it might seem.
+<p> <li> <a href="#mouseDoubleClickEvent">mouseDoubleClickEvent</a>() - 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
-tquite steady), a mouse release event and finally this event. It is
+quite steady), a mouse release event and finally this event. It is
<em>not possible</em> 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,
@@ -855,7 +855,7 @@ no matter if the widget is visible or not.
last visible top level widget is closed.
<p> Note that closing the <a href="qapplication.html#mainWidget">TQApplication::mainWidget</a>() terminates the
application.
-<p> <p>See also <a href="#closeEvent">closeEvent</a>(), <a href="qcloseevent.html">TQCloseEvent</a>, <a href="#hide">hide</a>(), <a href="qapplication.html#tquit">TQApplication::tquit</a>(), <a href="qapplication.html#setMainWidget">TQApplication::setMainWidget</a>(), and <a href="qapplication.html#lastWindowClosed">TQApplication::lastWindowClosed</a>().
+<p> <p>See also <a href="#closeEvent">closeEvent</a>(), <a href="qcloseevent.html">TQCloseEvent</a>, <a href="#hide">hide</a>(), <a href="qapplication.html#quit">TQApplication::quit</a>(), <a href="qapplication.html#setMainWidget">TQApplication::setMainWidget</a>(), and <a href="qapplication.html#lastWindowClosed">TQApplication::lastWindowClosed</a>().
<h3 class=fn>void <a name="closeEvent"></a>TQWidget::closeEvent ( <a href="qcloseevent.html">TQCloseEvent</a>&nbsp;*&nbsp;e )<tt> [virtual protected]</tt>
</h3>