summaryrefslogtreecommitdiffstats
path: root/doc/html/simple-application.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/html/simple-application.html')
-rw-r--r--doc/html/simple-application.html12
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/html/simple-application.html b/doc/html/simple-application.html
index eb9fd6968..165f1971a 100644
--- a/doc/html/simple-application.html
+++ b/doc/html/simple-application.html
@@ -68,7 +68,7 @@ public:
~ApplicationWindow();
protected:
- void closeEvent( <a href="qcloseevent.html">TQCloseEvent</a>* );
+ void closeEvent( <a href="tqcloseevent.html">TQCloseEvent</a>* );
private slots:
void newDoc();
@@ -500,14 +500,14 @@ TQSimpleRichText page at a time.
<p> Now let's see what happens when a user wishes to <em>close()</em>
an <em>ApplicationWindow</em>.
<p> <a name="closeEvent"></a>
-<pre> void ApplicationWindow::<a href="tqwidget.html#closeEvent">closeEvent</a>( <a href="qcloseevent.html">TQCloseEvent</a>* ce )
+<pre> void ApplicationWindow::<a href="tqwidget.html#closeEvent">closeEvent</a>( <a href="tqcloseevent.html">TQCloseEvent</a>* ce )
{
</pre>
<p> This event gets to process window system close events. A close event is
subtly different from a hide event: hide often means "iconify" whereas
close means that the window is going away for good.
<p> <pre> if ( !e-&gt;<a href="tqtextedit.html#isModified">isModified</a>() ) {
- ce-&gt;<a href="qcloseevent.html#accept">accept</a>();
+ ce-&gt;<a href="tqcloseevent.html#accept">accept</a>();
return;
}
</pre>
@@ -523,19 +523,19 @@ the widget will be deleted.
<p> Otherwise we ask the user: What do you want to do?
<p> <pre> case 0:
save();
- ce-&gt;<a href="qcloseevent.html#accept">accept</a>();
+ ce-&gt;<a href="tqcloseevent.html#accept">accept</a>();
break;
</pre>
<p> If they want to save and then exit, we do that.
<p> <pre> case 1:
- ce-&gt;<a href="qcloseevent.html#accept">accept</a>();
+ ce-&gt;<a href="tqcloseevent.html#accept">accept</a>();
break;
</pre>
<p> If the user doesn't want to exit, we ignore the close event (there is
a chance that we can't block it but we try).
<p> <pre> case 2:
default: // just for sanity
- ce-&gt;<a href="qcloseevent.html#ignore">ignore</a>();
+ ce-&gt;<a href="tqcloseevent.html#ignore">ignore</a>();
break;
</pre>
<p> The last case -- the user wants to abandon the edits and exit -- is very