Rename ntqapplication, ntqconfig and ntqmodules files to equivalent tq*

Signed-off-by: Michele Calgaro <[email protected]>

1 files changed, 11 insertions, 11 deletions

diff --git a/doc/html/tqsessionmanager.html b/doc/html/tqsessionmanager.html
index eb8ab42d5..d918c5f2f 100644
--- a/doc/html/tqsessionmanager.html
+++ b/doc/html/tqsessionmanager.html
@@ -74,8 +74,8 @@ etc.
 <p> TQSessionManager provides an interface between the application and
 the session manager so that the program can work well with the
 session manager. In TQt, session management requests for action
-are handled by the two virtual functions <a href="ntqapplication.html#commitData">TQApplication::commitData</a>()
-and <a href="ntqapplication.html#saveState">TQApplication::saveState</a>(). Both provide a reference to
+are handled by the two virtual functions <a href="tqapplication.html#commitData">TQApplication::commitData</a>()
+and <a href="tqapplication.html#saveState">TQApplication::saveState</a>(). Both provide a reference to
 a session manager object as argument, to allow the application
 to communicate with the session manager.
 <p> During a session management action (i.e. within commitData() and
@@ -141,7 +141,7 @@ released when the application exits.)
 <p> If the user decides to cancel the shutdown process during the
 interaction phase, you must tell the session manager that this has
 happened by calling <a href="#cancel">cancel</a>().
-<p> Here's an example of how an application's <a href="ntqapplication.html#commitData">TQApplication::commitData</a>()
+<p> Here's an example of how an application's <a href="tqapplication.html#commitData">TQApplication::commitData</a>()
 might be implemented:
 <p> <pre>
 void MyApplication::commitData( TQSessionManager&amp; sm ) {
@@ -173,7 +173,7 @@ void MyApplication::commitData( TQSessionManager&amp; sm ) {
  
 <p> If an error occurred within the application while saving its data,
 you may want to try <a href="#allowsErrorInteraction">allowsErrorInteraction</a>() instead.
-<p> <p>See also <a href="ntqapplication.html#commitData">TQApplication::commitData</a>(), <a href="#release">release</a>(), and <a href="#cancel">cancel</a>().
+<p> <p>See also <a href="tqapplication.html#commitData">TQApplication::commitData</a>(), <a href="#release">release</a>(), and <a href="#cancel">cancel</a>().
 
 <h3 class=fn>void <a name="cancel"></a>TQSessionManager::cancel ()
 </h3>
@@ -224,7 +224,7 @@ interaction phase.
 
 <p> Requests a second session management phase for the application. The
 application may then return immediately from the
-<a href="ntqapplication.html#commitData">TQApplication::commitData</a>() or <a href="ntqapplication.html#saveState">TQApplication::saveState</a>() function,
+<a href="tqapplication.html#commitData">TQApplication::commitData</a>() or <a href="tqapplication.html#saveState">TQApplication::saveState</a>() function,
 and they will be called again once most or all other applications have
 finished their session management.
 <p> The two phases are useful for applications such as the X11 window manager
@@ -266,7 +266,7 @@ iterate over a copy, e.g.
 <p> Returns the identifier of the current session.
 <p> If the application has been restored from an earlier session, this
 identifier is the same as it was in that earlier session.
-<p> <p>See also <a href="#sessionKey">sessionKey</a>() and <a href="ntqapplication.html#sessionId">TQApplication::sessionId</a>().
+<p> <p>See also <a href="#sessionKey">sessionKey</a>() and <a href="tqapplication.html#sessionId">TQApplication::sessionId</a>().
 
 <h3 class=fn><a href="tqstring.html">TQString</a> <a name="sessionKey"></a>TQSessionManager::sessionKey () const
 </h3>
@@ -276,7 +276,7 @@ identifier is the same as it was in that earlier session.
 key is the same as it was when the previous session ended.
 <p> The session key changes with every call of commitData() or
 saveState().
-<p> <p>See also <a href="#sessionId">sessionId</a>() and <a href="ntqapplication.html#sessionKey">TQApplication::sessionKey</a>().
+<p> <p>See also <a href="#sessionId">sessionId</a>() and <a href="tqapplication.html#sessionKey">TQApplication::sessionKey</a>().
 
 <h3 class=fn>void <a name="setDiscardCommand"></a>TQSessionManager::setDiscardCommand ( const&nbsp;<a href="tqstringlist.html">TQStringList</a>&nbsp;&amp; )
 </h3>
@@ -307,10 +307,10 @@ defaults to
         appname -session id
   </pre>
  
-<p> The <tt>-session</tt> option is mandatory; otherwise <a href="ntqapplication.html">TQApplication</a> cannot
+<p> The <tt>-session</tt> option is mandatory; otherwise <a href="tqapplication.html">TQApplication</a> cannot
 tell whether it has been restored or what the current session
-identifier is. See <a href="ntqapplication.html#isSessionRestored">TQApplication::isSessionRestored</a>() and
-<a href="ntqapplication.html#sessionId">TQApplication::sessionId</a>() for details.
+identifier is. See <a href="tqapplication.html#isSessionRestored">TQApplication::isSessionRestored</a>() and
+<a href="tqapplication.html#sessionId">TQApplication::sessionId</a>() for details.
 <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
@@ -327,7 +327,7 @@ session.
 startup the hint is set to <a href="#RestartHint-enum">RestartIfRunning</a>.
 <p> Note that these flags are only hints, a session manager may or may
 not respect them.
-<p> We recommend setting the restart hint in <a href="ntqapplication.html#saveState">TQApplication::saveState</a>()
+<p> We recommend setting the restart hint in <a href="tqapplication.html#saveState">TQApplication::saveState</a>()
 because most session managers perform a checkpoint shortly after an
 application's startup.
 <p> <p>See also <a href="#restartHint">restartHint</a>().