diff options
Diffstat (limited to 'doc/man/man3/tqsessionmanager.3qt')
| -rw-r--r-- | doc/man/man3/tqsessionmanager.3qt | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/doc/man/man3/tqsessionmanager.3qt b/doc/man/man3/tqsessionmanager.3qt index 57edd4fdf..070972691 100644 --- a/doc/man/man3/tqsessionmanager.3qt +++ b/doc/man/man3/tqsessionmanager.3qt @@ -75,7 +75,7 @@ The TQSessionManager class provides access to the session manager. .PP The session manager is responsible for session management, most importantly for interruption and resumption. A "session" is a kind 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 TQSettings to save and restore an individual application's settings, e.g. window positions, recently used files, etc. .PP -TQSessionManager provides an interface between the application and the session manager so that the program can work well with the session manager. In Qt, session management requests for action are handled by the two virtual functions QApplication::commitData() and QApplication::saveState(). Both provide a reference to a session manager object as argument, to allow the application to communicate with the session manager. +TQSessionManager provides an interface between the application and the session manager so that the program can work well with the session manager. In Qt, session management requests for action are handled by the two virtual functions TQApplication::commitData() and TQApplication::saveState(). Both provide a reference to a session manager object as argument, to allow the application to communicate with the session manager. .PP During a session management action (i.e. within commitData() and saveState()), no user interaction is possible \fIunless\fR the application got explicit permission from the session manager. You ask for permission by calling allowsInteraction() or, if it's really urgent, allowsErrorInteraction(). TQt does not enforce this, but the session manager may. .PP @@ -111,7 +111,7 @@ When the interaction is completed we strongly recommend releasing the user inter .PP 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 cancel(). .PP -Here's an example of how an application's QApplication::commitData() might be implemented: +Here's an example of how an application's TQApplication::commitData() might be implemented: .PP .nf .br @@ -168,7 +168,7 @@ void MyApplication::commitData( TQSessionManager& sm ) { .PP If an error occurred within the application while saving its data, you may want to try allowsErrorInteraction() instead. .PP -See also QApplication::commitData(), release(), and cancel(). +See also TQApplication::commitData(), release(), and cancel(). .SH "void TQSessionManager::cancel ()" Tells the session manager to cancel the shutdown process. Applications should not call this function without first asking the user. .PP @@ -206,7 +206,7 @@ Releases the session manager's interaction semaphore after an interaction phase. .PP See also allowsInteraction() and allowsErrorInteraction(). .SH "void TQSessionManager::requestPhase2 ()" -Requests a second session management phase for the application. The application may then return immediately from the QApplication::commitData() or QApplication::saveState() function, and they will be called again once most or all other applications have finished their session management. +Requests a second session management phase for the application. The application may then return immediately from the TQApplication::commitData() or TQApplication::saveState() function, and they will be called again once most or all other applications have finished their session management. .PP The two phases are useful for applications such as the X11 window manager that need to store information about another application's windows and therefore have to wait until these applications have completed their respective session management tasks. .PP @@ -244,7 +244,7 @@ Returns the identifier of the current session. .PP If the application has been restored from an earlier session, this identifier is the same as it was in that earlier session. .PP -See also sessionKey() and QApplication::sessionId(). +See also sessionKey() and TQApplication::sessionId(). .SH "TQString TQSessionManager::sessionKey () const" Returns the session key in the current session. .PP @@ -252,7 +252,7 @@ If the application has been restored from an earlier session, this key is the sa .PP The session key changes with every call of commitData() or saveState(). .PP -See also sessionId() and QApplication::sessionKey(). +See also sessionId() and TQApplication::sessionKey(). .SH "void TQSessionManager::setDiscardCommand ( const TQStringList & )" See also discardCommand() and setRestartCommand(). .SH "void TQSessionManager::setManagerProperty ( const TQString & name, const TQStringList & value )" @@ -274,7 +274,7 @@ If the session manager is capable of restoring sessions it will execute \fIcomma .br .fi .PP -The \fC-session\fR option is mandatory; otherwise QApplication cannot tell whether it has been restored or what the current session identifier is. See QApplication::isSessionRestored() and QApplication::sessionId() for details. +The \fC-session\fR option is mandatory; otherwise TQApplication cannot tell whether it has been restored or what the current session identifier is. See TQApplication::isSessionRestored() and TQApplication::sessionId() for details. .PP 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 TQSettings, or temporary files or a database for this purpose. By marking the data with the unique sessionId(), you will be able to restore the application in a future session. .PP @@ -284,7 +284,7 @@ Sets the application's restart hint to \fIhint\fR. On application startup the hi .PP Note that these flags are only hints, a session manager may or may not respect them. .PP -We recommend setting the restart hint in QApplication::saveState() because most session managers perform a checkpoint shortly after an application's startup. +We recommend setting the restart hint in TQApplication::saveState() because most session managers perform a checkpoint shortly after an application's startup. .PP See also restartHint(). |