Update to latest tqt3 automated conversion

1 files changed, 11 insertions, 11 deletions

diff --git a/doc/html/session.html b/doc/html/session.html
index 3cd66010c..2e1505157 100644
--- a/doc/html/session.html
+++ b/doc/html/session.html
@@ -64,33 +64,33 @@ the machine!
 management for applications yet, i.e. no restoring of previous
 sessions. They do support graceful logouts where applications
 have the opportunity to cancel the process after getting confirmation
-from the user. This is the functionality that corresponds to the <a href="qapplication.html#commitData">TQApplication::commitData</a>() method.
+from the user. This is the functionality that corresponds to the <a href="ntqapplication.html#commitData">TQApplication::commitData</a>() method.
 <p> X11 has supported complete session management since X11R6.
 <p> <h2>  Getting session management to work with TQt 
 </h2>
-<a name="4"></a><p> Start by reimplementing <a href="qapplication.html#commitData">TQApplication::commitData</a>() to
+<a name="4"></a><p> Start by reimplementing <a href="ntqapplication.html#commitData">TQApplication::commitData</a>() to
 enable your application to take part in the graceful logout process. If
 you are only targeting the MS-Windows platform, this is all you can
 and must provide. Ideally, your application should provide a shutdown
 dialog similar to the following:
 <p> <center><img src="session.png" alt="A typical dialog on shutdown"></center> 
-<p> Example code to this dialog can be found in the documentation of <a href="qsessionmanager.html#allowsInteraction">TQSessionManager::allowsInteraction</a>().
+<p> Example code to this dialog can be found in the documentation of <a href="ntqsessionmanager.html#allowsInteraction">TQSessionManager::allowsInteraction</a>().
 <p> For complete session management (only supported on X11R6 at present),
 you must also take care of saving the application's state, and
 potentially of restoring the state in the next life cycle of the
-session. This saving is done by reimplementing <a href="qapplication.html#saveState">TQApplication::saveState</a>(). All state data you are saving in this
-function, should be marked with the session identifier <a href="qapplication.html#sessionId">TQApplication::sessionId</a>(). This application specific identifier is
-globally unique, so no clashes will occur. (See <a href="qsessionmanager.html">TQSessionManager</a> for
+session. This saving is done by reimplementing <a href="ntqapplication.html#saveState">TQApplication::saveState</a>(). All state data you are saving in this
+function, should be marked with the session identifier <a href="ntqapplication.html#sessionId">TQApplication::sessionId</a>(). This application specific identifier is
+globally unique, so no clashes will occur. (See <a href="ntqsessionmanager.html">TQSessionManager</a> for
 information on saving/restoring the state of a particular TQt
 application.)
 <p> Restoration is usually done in the application's main()
-function. Check if <a href="qapplication.html#isSessionRestored">TQApplication::isSessionRestored</a>() is <tt>TRUE</tt>. If
-that's the case, use the session identifier <a href="qapplication.html#sessionId">TQApplication::sessionId</a>() again to access your state data and restore
+function. Check if <a href="ntqapplication.html#isSessionRestored">TQApplication::isSessionRestored</a>() is <tt>TRUE</tt>. If
+that's the case, use the session identifier <a href="ntqapplication.html#sessionId">TQApplication::sessionId</a>() again to access your state data and restore
 the state of the application.
 <p> <strong>Important:</strong> In order to allow the window manager to
 restore window attributes such as stacking order or geometry
 information, you must identify your top level widgets with 
-unique application-wide object names (see <a href="qobject.html#setName">TQObject::setName</a>()). When
+unique application-wide object names (see <a href="ntqobject.html#setName">TQObject::setName</a>()). When
 restoring the application, you must ensure that all restored
 top level widgets are given the same unique names they had before.
 <p> <h2>  Testing and debugging session management 
@@ -135,8 +135,8 @@ crash.
 <li> Use the session manager's <em>Checkpoint</em> and <em>Shutdown</em> buttons
 with different settings and see how your application behaves. The save
 type <em>local</em> means that the clients should save their state. It
-corresponds to the <a href="qapplication.html#saveState">TQApplication::saveState</a>() function. The <em>global</em> save type asks applications to save their unsaved changes in
-permanent, globally accessible storage. It invokes <a href="qapplication.html#commitData">TQApplication::commitData</a>().
+corresponds to the <a href="ntqapplication.html#saveState">TQApplication::saveState</a>() function. The <em>global</em> save type asks applications to save their unsaved changes in
+permanent, globally accessible storage. It invokes <a href="ntqapplication.html#commitData">TQApplication::commitData</a>().
 <li> Whenever something crashes, blame <tt>xsm</tt> and not TQt. <tt>xsm</tt> is far
 from being a usable session manager on a user's desktop. It is,
 however, stable and useful enough to serve as testing environment.