Session Management

When we log out on X11, some window managers ask us whether we want to save the session. If we say yes, the applications that were running are automatically restarted the next time we log in, with the same screen positions and, ideally, with the same state as they had when we logged out.

The X11-specific component that takes care of saving and restoring the session is called the session manager. To make a Qt application aware of the session manager, we must reimplement QApplication::saveState() and save the application's state there.

Figure 18.6. Logging out on KDE

graphics/18fig06.gif

Windows 2000 and XP (and some Unix systems) offer a different mechanism, called hibernation. When the user puts the computer into hibernation, the operating system simply dumps the computer's memory onto disk and reloads it on startup. Applications do not need to do anything or even be aware that this happens.

When the user initiates a shutdown, we can take control just before the shutdown occurs by reimplementing QApplication::commitData(). This allows us to save any unsaved data and to interact with the user if required. This works the same way on both X11 and Windows.

We will explore session management by going through the code of a sessionaware Tic-Tac-Toe application. First, let's look at the main() function:

int main(int argc, char *argv[])
{
 Application app(argc, argv);
 TicTacToe tic(0, "tic");
 app.setTicTacToe(&tic);
 tic.show();
 return app.exec();
}

We create an Application object. The Application class inherits from QApplication and reimplements both commitData() and saveState() to support session management.

Next, we create a TicTacToe widget, make the Application object aware of it, and show it. We have called the TicTacToe widget "tic". We must give unique names to top-level widgets if we want the session manager to restore the windows' sizes and positions.

Figure 18.7. The Tic-Tac-Toe application

graphics/18fig07.gif

Here's the definition of the Application class:

class Application : public QApplication
{
 Q_OBJECT
public:
 Application(int &argc, char *argv[]);

 void setTicTacToe(TicTacToe *tic);
 void commitData(QSessionManager &sessionManager);
 void saveState(QSessionManager &sessionManager);

private:
 TicTacToe *ticTacToe;
};

The Application class keeps a pointer to the TicTacToe widget as a private variable.

void Application::saveState(QSessionManager &sessionManager)
{
 QString fileName = ticTacToe->saveState();

 QStringList discardCommand;
 discardCommand << "rm" << fileName;
 sessionManager.setDiscardCommand(discardCommand);
}

On X11, the saveState() function is called when the session manager wants the application to save its state. The function is available on other platforms as well, but it is never called. The QSessionManager parameter allows us to communicate with the session manager.

We start by asking the TicTacToe widget to save its state to a file. Then we set the session manager's discard command. A discard command is a command that the session manager must execute to delete any stored information regarding the current state. For this example, we set it to

rm file

where file is the name of the file that contains the saved state for the session, and rm is the standard Unix command to remove files.

The session manager also has a restart command. This is the command that the session manager must execute to restart the application. By default, Qt provides the following restart command:

appname -session id_key

The first part, appname, is derived from argv[0]. The id part is the session ID provided by the session manager; it is guaranteed to be unique among different applications and among different runs of the same application. The key part comes in addition to uniquely identify the time at which the state was saved. For various reasons, the session manager can call saveState() multiple times during the same session, and the different states must be distinguished.

Because of limitations in existing session managers, we need to make sure that the application's directory is in the PATH environment variable if we want the application to restart correctly. In particular, if you want to try out the Tic-Tac-Toe example for yourself, you must install it in, say, /usr/bin and invoke it as tictactoe.

For simple applications, including Tic-Tac-Toe, we could save the state as an additional command-line argument to the restart command. For example:

tictactoe -state OX-XO-X-O

This would save us from storing the data in a file and providing a discard command to remove the file.

void Application::commitData(QSessionManager &sessionManager)
{
 if (ticTacToe->gameInProgress()
 && sessionManager.allowsInteraction()) {
 int ret = QMessageBox::warning(ticTacToe, tr("Tic-Tac-Toe"),
 tr("The game hasn't finished.
"
 "Do you really want to quit?"),
 QMessageBox::Yes | QMessageBox::Default,
 QMessageBox::No | QMessageBox::Escape);
 if (ret == QMessageBox::Yes)
 sessionManager.release();
 else
 sessionManager.cancel();
 }
}

The commitData() function is called when the user logs out. We can reimplement it to pop up a message box warning the user about potential data loss. The default implementation closes all top-level widgets, which results in the same behavior as when the user closes the windows one after another by clicking the X button in their title bars. In Chapter 3, we saw how to reimplement closeEvent() to catch this and pop up a message box.

For the purposes of this example, we reimplement commitData() and pop up a message box asking the user to confirm the log out if a game is in progress and if the session manager allows us to interact with the user. If the user clicks Yes, we call release() to tell the session manager to continue logging out; if the user clicks No, we call cancel() to cancel the log out.

Figure 18.8. "Do you really want to quit?"

graphics/18fig08.gif

Now let's look at the TicTacToe class:

class TicTacToe : public QWidget
{
 Q_OBJECT
public:
 TicTacToe(QWidget *parent = 0, const char *name = 0);

 QSize sizeHint() const;
 bool gameInProgress() const;
 QString saveState() const;

protected:
 void paintEvent(QPaintEvent *event);
 void mousePressEvent(QMouseEvent *event);

private:
 enum { Empty ='-', Cross = 'X', Nought = 'O' };

 void clearBoard();
 void restoreState();
 QString sessionFileName() const;
 QRect cellRect(int row, int col) const;
 int cellWidth() const { return width() / 3;}
 int cellHeight() const { return height() / 3;}

 char board[3][3];
 int turnNumber;
};

The TicTacToe class inherits from QWidget and reimplements sizeHint(), paintEvent(), and mousePressEvent(). It also provides the gameInProgress() and saveState() functions that we used in Application.

TicTacToe::TicTacToe(QWidget *parent, const char *name)
 : QWidget(parent, name)
{
 setCaption(tr("Tic-Tac-Toe"));
 clearBoard();
 if (qApp->isSessionRestored())
 restoreState();
}

In the constructor, we clear the board, and if the application was invoked with the -session option, we call the private function restoreState() to reload the old session.

void TicTacToe::clearBoard()
{
 for (int row = 0; row < 3; ++row) {
 for (int col = 0; col < 3; ++col) {
 board[row] [col] = Empty;
 }
 }
 turnNumber = 0;
}

In clearBoard(), we clear all the cells and set turnNumber to 0.

QString TicTacToe::saveState() const
{
 QFile file(sessionFileName());
 if (file.open(IO_WriteOnly)) {
 QTextStream out(&file);
 for (int row = 0; row < 3; ++row) {
 for (int col = 0; col < 3; ++col) {
 out << board[row] [col];
 }
 }
 }
 return file.name();
}

In saveState(), we write the state of the board to disk. The format is straighforward, with 'X'for crosses, 'O' for noughts, and '-' for empty cells.

QString TicTacToe::sessionFileName() const
{
 return QDir::homeDirPath() + "/.tictactoe_"
 + qApp->sessionId() +"_" + qApp->sessionKey();
}

The sessionFileName() private function returns the file name for the current session ID and session key. This function is used for both saveState() and restoreState(). The file name is derived from the session ID and session key.

void TicTacToe::restoreState()
{
 QFile file(sessionFileName());
 if (file.open(IO_ReadOnly)) {
 QTextStream in(&file);
 for (int row = 0; row < 3; ++row) {
 for (int col = 0; col < 3; ++col) {
 in >> board[row][col];
 if (board[row][col] != Empty)
 ++turnNumber;
 }
 }
 }
 repaint();
}

In restoreState(), we load the file that corresponds to the restored session and fill the board with that information. We deduce the value of turnNumber from the number of X's and O's the board.

In the TicTacToe constructor, we called restoreState() if QApplication::isSessionRestored() returned true. In that case, sessionId() and sessionKey() return the same values as when the application's state was saved, and so sessionFileName() returns the file name for that session.

Testing and debugging session management can be frustrating, because we need to log in and out all the time. One way to avoid this is to use the standard xsm utility provided with X11. The first time we invoke xsm, it pops up a session manager window and a terminal. The applications we start from that terminal will all use xsm as their session manager instead of the usual, system-wide session manager. We can then use xsm's window to end, restart, or discard a session, and see if our application behaves as it should. For details about how to do this, see http://doc.trolltech.com/3.2/session.html.

Part I: Basic Qt

Getting Started

Creating Dialogs

Creating Main Windows

Implementing Application Functionality

Creating Custom Widgets

Part II: Intermediate Qt

Layout Management

Event Processing

2D and 3D Graphics

Drag and Drop

Input/Output

Container Classes

Databases

Networking

XML

Internationalization

Providing Online Help

Multithreading

Platform-Specific Features



C++ GUI Programming with Qt 3
C++ GUI Programming with Qt 3
ISBN: 0131240722
EAN: 2147483647
Year: 2006
Pages: 140

Similar book on Amazon

Flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net