summaryrefslogtreecommitdiffstats
path: root/doc/html/tqsessionmanager.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/html/tqsessionmanager.html')
-rw-r--r--doc/html/tqsessionmanager.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/html/tqsessionmanager.html b/doc/html/tqsessionmanager.html
index 28e10d69f..bc759fe82 100644
--- a/doc/html/tqsessionmanager.html
+++ b/doc/html/tqsessionmanager.html
@@ -69,7 +69,7 @@ of record of the state of the system, e.g. which applications were
run at start up and which applications are currently running. The
session manager is used to save the session, e.g. when the machine
is shut down; and to restore a session, e.g. when the machine is
-started up. Use <a href="ntqsettings.html">TQSettings</a> to save and restore an individual
+started up. Use <a href="tqsettings.html">TQSettings</a> to save and restore an individual
application's settings, e.g. window positions, recently used files,
etc.
<p> TQSessionManager provides an interface between the application and
@@ -315,7 +315,7 @@ identifier is. See <a href="ntqapplication.html#isSessionRestored">TQApplication
<p> If your application is very simple, it may be possible to store the
entire application state in additional command line options. This
is usually a very bad idea because command lines are often limited
-to a few hundred bytes. Instead, use <a href="ntqsettings.html">TQSettings</a>, or temporary files
+to a few hundred bytes. Instead, use <a href="tqsettings.html">TQSettings</a>, or temporary files
or a database for this purpose. By marking the data with the unique
<a href="#sessionId">sessionId</a>(), you will be able to restore the application in a future
session.