- Qt 6.4
- Qt Widgets
- Main Window Examples
- Qt Widgets - Application Example
- Qt 6.4.3 Reference Documentation

# Qt Widgets - Application Example

The Application example shows how to implement a standard widget application with menus, toolbars, and a status bar. The example itself is a simple text editor program built around QPlainTextEdit.

Nearly all of the code for the Application example is in the `MainWindow` class, which inherits QMainWindow. QMainWindow provides the framework for windows that have menus, toolbars, dock windows, and a status bar. The application provides File, Edit, and Help entries in the menu bar, with the following popup menus:

The status bar at the bottom of the main window shows a description of the menu item or toolbar button under the cursor.

To keep the example simple, recently opened files aren't shown in the File menu, even though this feature is desired in 90% of applications. Furthermore, this example can only load one file at a time. The SDI and MDI examples show how to lift these restrictions and how to implement recently opened files handling.

#### MainWindow Class Definition

Here's the class definition:

     class MainWindow : public QMainWindow
     {
         Q_OBJECT

     public:
         MainWindow();

         void loadFile(const QString &fileName);

     protected:
         void closeEvent(QCloseEvent *event) override;

     private slots:
         void newFile();
         void open();
         bool save();
         bool saveAs();
         void about();
         void documentWasModified();
     #ifndef QT_NO_SESSIONMANAGER
         void commitData(QSessionManager &);
     #endif

     private:
         void createActions();
         void createStatusBar();
         void readSettings();
         void writeSettings();
         bool maybeSave();
         bool saveFile(const QString &fileName);
         void setCurrentFile(const QString &fileName);
         QString strippedName(const QString &fullFileName);

         QPlainTextEdit *textEdit;
         QString curFile;
     };

The public API is restricted to the constructor. In the `protected` section, we reimplement QWidget::closeEvent() to detect when the user attempts to close the window, and warn the user about unsaved changes. In the `private slots` section, we declare slots that correspond to menu entries, as well as a mysterious `documentWasModified()` slot. Finally, in the `private` section of the class, we have various members that will be explained in due time.

#### MainWindow Class Implementation

     #include <QtWidgets>

     #include "mainwindow.h"

We start by including `<QtWidgets>`, a header file that contains the definition of all classes in the Qt Core, Qt GUI and Qt Widgets modules. This saves us from the trouble of having to include every class individually. We also include `mainwindow.h`.

You might wonder why we don't include `<QtWidgets>` in `mainwindow.h` and be done with it. The reason is that including such a large header from another header file can rapidly degrade performances. Here, it wouldn't do any harm, but it's still generally a good idea to include only the header files that are strictly necessary from another header file.

     MainWindow::MainWindow()
         : textEdit(new QPlainTextEdit)
     {
         setCentralWidget(textEdit);

         createActions();
         createStatusBar();

         readSettings();

         connect(textEdit->document(), &QTextDocument::contentsChanged,
                 this, &MainWindow::documentWasModified);

     #ifndef QT_NO_SESSIONMANAGER
         connect(qApp, &QGuiApplication::commitDataRequest,
                 this, &MainWindow::commitData);
     #endif

         setCurrentFile(QString());
         setUnifiedTitleAndToolBarOnMac(true);
     }

In the constructor, we start by creating a QPlainTextEdit widget as a child of the main window (the `this` object). Then we call QMainWindow::setCentralWidget() to tell that this is going to be the widget that occupies the central area of the main window, between the toolbars and the status bar.

Then we call `createActions()` and `createStatusBar()`, two private functions that set up the user interface. After that, we call `readSettings()` to restore the user's preferences.

We establish a signal-slot connection between the QPlainTextEdit's document object and our `documentWasModified()` slot. Whenever the user modifies the text in the QPlainTextEdit, we want to update the title bar to show that the file was modified.

At the end, we set the window title using the private `setCurrentFile()` function. We'll come back to this later.

     void MainWindow::closeEvent(QCloseEvent *event)
     {
         if (maybeSave()) {
             writeSettings();
             event->accept();
         } else {
             event->ignore();
         }
     }

When the user attempts to close the window, we call the private function `maybeSave()` to give the user the possibility to save pending changes. The function returns true if the user wants the application to close; otherwise, it returns false. In the first case, we save the user's preferences to disk and accept the close event; in the second case, we ignore the close event, meaning that the application will stay up and running as if nothing happened.

     void MainWindow::newFile()
     {
         if (maybeSave()) {
             textEdit->clear();
             setCurrentFile(QString());
         }
     }

The `newFile()` slot is invoked when the user selects File|New from the menu. We call `maybeSave()` to save any pending changes and if the user accepts to go on, we clear the QPlainTextEdit and call the private function `setCurrentFile()` to update the window title and clear the windowModified flag.

     void MainWindow::open()
     {
         if (maybeSave()) {
             QString fileName = QFileDialog::getOpenFileName(this);
             if (!fileName.isEmpty())
                 loadFile(fileName);
         }
     }

The `open()` slot is invoked when the user clicks File|Open. We pop up a QFileDialog asking the user to choose a file. If the user chooses a file (i.e., `fileName` is not an empty string), we call the private function `loadFile()` to actually load the file.

     bool MainWindow::save()
     {
         if (curFile.isEmpty()) {
             return saveAs();
         } else {
             return saveFile(curFile);
         }
     }

The `save()` slot is invoked when the user clicks File|Save. If the user hasn't provided a name for the file yet, we call `saveAs()`; otherwise, we call the private function `saveFile()` to actually save the file.

     bool MainWindow::saveAs()
     {
         QFileDialog dialog(this);
         dialog.setWindowModality(Qt::WindowModal);
         dialog.setAcceptMode(QFileDialog::AcceptSave);
         if (dialog.exec() != QDialog::Accepted)
             return false;
         return saveFile(dialog.selectedFiles().first());
     }

In `saveAs()`, we start by popping up a QFileDialog asking the user to provide a name. If the user clicks Cancel, the returned file name is empty, and we do nothing.

     void MainWindow::about()
     {
        QMessageBox::about(this, tr("About Application"),
                 tr("The <b>Application</b> example demonstrates how to "
                    "write modern GUI applications using Qt, with a menu bar, "
                    "toolbars, and a status bar."));
     }

The application's About box is done using one statement, using the QMessageBox::about() static function and relying on its support for an HTML subset.

The tr() call around the literal string marks the string for translation. It is a good habit to call tr() on all user-visible strings, in case you later decide to translate your application to other languages. The Internationalization with Qt overview covers tr() in more detail.

     void MainWindow::documentWasModified()
     {
         setWindowModified(textEdit->document()->isModified());
     }

The `documentWasModified()` slot is invoked each time the text in the QPlainTextEdit changes because of user edits. We call QWidget::setWindowModified() to make the title bar show that the file was modified. How this is done varies on each platform.

     void MainWindow::createActions()
     {

         QMenu *fileMenu = menuBar()->addMenu(tr("&File"));
         QToolBar *fileToolBar = addToolBar(tr("File"));
         const QIcon newIcon = QIcon::fromTheme("document-new", QIcon(":/images/new.png"));
         QAction *newAct = new QAction(newIcon, tr("&New"), this);
         newAct->setShortcuts(QKeySequence::New);
         newAct->setStatusTip(tr("Create a new file"));
         connect(newAct, &QAction::triggered, this, &MainWindow::newFile);
         fileMenu->addAction(newAct);
         fileToolBar->addAction(newAct);

         const QIcon openIcon = QIcon::fromTheme("document-open", QIcon(":/images/open.png"));
         QAction *openAct = new QAction(openIcon, tr("&Open..."), this);
         openAct->setShortcuts(QKeySequence::Open);
         openAct->setStatusTip(tr("Open an existing file"));
         connect(openAct, &QAction::triggered, this, &MainWindow::open);
         fileMenu->addAction(openAct);
         fileToolBar->addAction(openAct);
         ...
         QAction *aboutQtAct = helpMenu->addAction(tr("About &Qt"), qApp, &QApplication::aboutQt);
         aboutQtAct->setStatusTip(tr("Show the Qt library's About box"));

The `createActions()` private function, which is called from the `MainWindow` constructor, creates QActions and populates the menus and two toolbars. The code is very repetitive, so we show only the actions corresponding to File|New, File|Open, and Help|About Qt.

A QAction is an object that represents one user action, such as saving a file or invoking a dialog. An action can be put in a QMenu or a QToolBar, or both, or in any other widget that reimplements QWidget::actionEvent().

An action has a text that is shown in the menu, an icon, a shortcut key, a tooltip, a status tip (shown in the status bar), a "What's This?" text, and more. It emits a triggered() signal whenever the user invokes the action (e.g., by clicking the associated menu item or toolbar button).

Instances of QAction can be created by passing a parent QObject or by using one of the convenience functions of QMenu, QMenuBar or QToolBar. We create the actions that are in a menu as well as in a toolbar parented on the window to prevent ownership issues. For actions that are only in the menu, we use the convenience function QMenu::addAction(), which allows us to pass text, icon and the target object and its slot member function.

Creating toolbars is very similar to creating menus. The same actions that we put in the menus can be reused in the toolbars. After creating the action, we add it to the toolbar using QToolBar::addAction().

The code above contains one more idiom that must be explained. For some of the actions, we specify an icon as a QIcon to the QAction constructor. We use QIcon::fromTheme() to obtain the correct standard icon from the underlying window system. If that fails due to the platform not supporting it, we pass a file name as fallback. Here, the file name starts with `:`. Such file names aren't ordinary file names, but rather path in the executable's stored resources. We'll come back to this when we review the `application.qrc` file that's part of the project.

     #ifndef QT_NO_CLIPBOARD
         cutAct->setEnabled(false);
         copyAct->setEnabled(false);
         connect(textEdit, &QPlainTextEdit::copyAvailable, cutAct, &QAction::setEnabled);
         connect(textEdit, &QPlainTextEdit::copyAvailable, copyAct, &QAction::setEnabled);
     #endif // !QT_NO_CLIPBOARD
     }

The Edit|Cut and Edit|Copy actions must be available only when the QPlainTextEdit contains selected text. We disable them by default and connect the QPlainTextEdit::copyAvailable() signal to the QAction::setEnabled() slot, ensuring that the actions are disabled when the text editor has no selection.

Just before we create the Help menu, we call QMenuBar::addSeparator(). This has no effect for most widget styles (e.g., Windows and macOS styles), but for some styles this makes sure that Help is pushed to the right side of the menu bar.

     void MainWindow::createStatusBar()
     {
         statusBar()->showMessage(tr("Ready"));
     }

QMainWindow::statusBar() returns a pointer to the main window's QStatusBar widget. Like with QMainWindow::menuBar(), the widget is automatically created the first time the function is called.

     void MainWindow::readSettings()
     {
         QSettings settings(QCoreApplication::organizationName(), QCoreApplication::applicationName());
         const QByteArray geometry = settings.value("geometry", QByteArray()).toByteArray();
         if (geometry.isEmpty()) {
             const QRect availableGeometry = screen()->availableGeometry();
             resize(availableGeometry.width() / 3, availableGeometry.height() / 2);
             move((availableGeometry.width() - width()) / 2,
                  (availableGeometry.height() - height()) / 2);
         } else {
             restoreGeometry(geometry);
         }
     }

The `readSettings()` function is called from the constructor to load the user's preferences and other application settings. The QSettings class provides a high-level interface for storing settings permanently on disk. On Windows, it uses the (in)famous Windows registry; on macOS, it uses the native XML-based CFPreferences API; on Unix/X11, it uses text files.

The QSettings constructor takes arguments that identify your company and the name of the product. This ensures that the settings for different applications are kept separately.

We use QSettings::value() to extract the value of the geometry setting. The second argument to QSettings::value() is optional and specifies a default value for the setting if there exists none. This value is used the first time the application is run.

We use QWidget::saveGeometry() and Widget::restoreGeometry() to save the position. They use an opaque QByteArray to store screen number, geometry and window state.

     void MainWindow::writeSettings()
     {
         QSettings settings(QCoreApplication::organizationName(), QCoreApplication::applicationName());
         settings.setValue("geometry", saveGeometry());
     }

The `writeSettings()` function is called from `closeEvent()`. Writing settings is similar to reading them, except simpler. The arguments to the QSettings constructor must be the same as in `readSettings()`.

     bool MainWindow::maybeSave()
     {
         if (!textEdit->document()->isModified())
             return true;
         const QMessageBox::StandardButton ret
             = QMessageBox::warning(this, tr("Application"),
                                    tr("The document has been modified.\n"
                                       "Do you want to save your changes?"),
                                    QMessageBox::Save | QMessageBox::Discard | QMessageBox::Cancel);
         switch (ret) {
         case QMessageBox::Save:
             return save();
         case QMessageBox::Cancel:
             return false;
         default:
             break;
         }
         return true;
     }

The `maybeSave()` function is called to save pending changes. If there are pending changes, it pops up a QMessageBox giving the user to save the document. The options are QMessageBox::Yes, QMessageBox::No, and QMessageBox::Cancel. The Yes button is made the default button (the button that is invoked when the user presses Return) using the QMessageBox::Default flag; the Cancel button is made the escape button (the button that is invoked when the user presses Esc) using the QMessageBox::Escape flag.

The `maybeSave()` function returns `true` in all cases, except when the user clicks Cancel or saving the file fails. The caller must check the return value and stop whatever it was doing if the return value is `false`.

     void MainWindow::loadFile(const QString &fileName)
     {
         QFile file(fileName);
         if (!file.open(QFile::ReadOnly | QFile::Text)) {
             QMessageBox::warning(this, tr("Application"),
                                  tr("Cannot read file %1:\n%2.")
                                  .arg(QDir::toNativeSeparators(fileName), file.errorString()));
             return;
         }

         QTextStream in(&file);
     #ifndef QT_NO_CURSOR
         QGuiApplication::setOverrideCursor(Qt::WaitCursor);
     #endif
         textEdit->setPlainText(in.readAll());
     #ifndef QT_NO_CURSOR
         QGuiApplication::restoreOverrideCursor();
     #endif

         setCurrentFile(fileName);
         statusBar()->showMessage(tr("File loaded"), 2000);
     }

In `loadFile()`, we use QFile and QTextStream to read in the data. The QFile object provides access to the bytes stored in a file.

We start by opening the file in read-only mode. The QFile::Text flag indicates that the file is a text file, not a binary file. On Unix and macOS, this makes no difference, but on Windows, it ensures that the "\r\n" end-of-line sequence is converted to "\n" when reading.

If we successfully opened the file, we use a QTextStream object to read in the data. QTextStream automatically converts the 8-bit data into a Unicode QString and supports various encodings. If no encoding is specified, QTextStream assumes the file is encoded in UTF-8.

Since the call to QTextStream::readAll() might take some time, we set the cursor to be Qt::WaitCursor for the entire application while it goes on.

At the end, we call the private `setCurrentFile()` function, which we'll cover in a moment, and we display the string "File loaded" in the status bar for 2 seconds (2000 milliseconds).

     bool MainWindow::saveFile(const QString &fileName)
     {
         QString errorMessage;

         QGuiApplication::setOverrideCursor(Qt::WaitCursor);
         QSaveFile file(fileName);
         if (file.open(QFile::WriteOnly | QFile::Text)) {
             QTextStream out(&file);
             out << textEdit->toPlainText();
             if (!file.commit()) {
                 errorMessage = tr("Cannot write file %1:\n%2.")
                                .arg(QDir::toNativeSeparators(fileName), file.errorString());
             }
         } else {
             errorMessage = tr("Cannot open file %1 for writing:\n%2.")
                            .arg(QDir::toNativeSeparators(fileName), file.errorString());
         }
         QGuiApplication::restoreOverrideCursor();

         if (!errorMessage.isEmpty()) {
             QMessageBox::warning(this, tr("Application"), errorMessage);
             return false;
         }

         setCurrentFile(fileName);
         statusBar()->showMessage(tr("File saved"), 2000);
         return true;
     }

Saving a file is similar to loading one. We use QSaveFile to ensure all data are safely written and existing files are not damaged should writing fail. We use the QFile::Text flag to make sure that on Windows, "\n" is converted into "\r\n" to conform to the Windows convention.

     void MainWindow::setCurrentFile(const QString &fileName)
     {
         curFile = fileName;
         textEdit->document()->setModified(false);
         setWindowModified(false);

         QString shownName = curFile;
         if (curFile.isEmpty())
             shownName = "untitled.txt";
         setWindowFilePath(shownName);
     }

The `setCurrentFile()` function is called to reset the state of a few variables when a file is loaded or saved, or when the user starts editing a new file (in which case `fileName` is empty). We update the `curFile` variable, clear the QTextDocument::modified flag and the associated `QWidget:windowModified` flag, and update the window title to contain the new file name (or `untitled.txt`).

The `strippedName()` function call around `curFile` in the QWidget::setWindowTitle() call shortens the file name to exclude the path. Here's the function:

     QString MainWindow::strippedName(const QString &fullFileName)
     {
         return QFileInfo(fullFileName).fileName();
     }

#### The main() Function

The `main()` function for this application is typical of applications that contain one main window:

     #include <QApplication>
     #include <QCommandLineParser>
     #include <QCommandLineOption>

     #include "mainwindow.h"

     int main(int argc, char *argv[])
     {
         Q_INIT_RESOURCE(application);

         QApplication app(argc, argv);
         QCoreApplication::setOrganizationName("QtProject");
         QCoreApplication::setApplicationName("Application Example");
         QCoreApplication::setApplicationVersion(QT_VERSION_STR);
         QCommandLineParser parser;
         parser.setApplicationDescription(QCoreApplication::applicationName());
         parser.addHelpOption();
         parser.addVersionOption();
         parser.addPositionalArgument("file", "The file to open.");
         parser.process(app);

         MainWindow mainWin;
         if (!parser.positionalArguments().isEmpty())
             mainWin.loadFile(parser.positionalArguments().first());
         mainWin.show();
         return app.exec();
     }

The main function uses QCommandLineParser to check whether some file argument was passed to the application and loads it via MainWindow::loadFile().

#### The Resource File

As you will probably recall, for some of the actions, we specified icons with file names starting with `:` and mentioned that such file names aren't ordinary file names, but path in the executable's stored resources. These resources are compiled

The resources associated with an application are specified in a `.qrc` file, an XML-based file format that lists files on the disk. Here's the `application.qrc` file that's used by the Application example:

     <!DOCTYPE RCC><RCC version="1.0">
     <qresource>
         <file>images/copy.png</file>
         <file>images/cut.png</file>
         <file>images/new.png</file>
         <file>images/open.png</file>
         <file>images/paste.png</file>
         <file>images/save.png</file>
     </qresource>
     </RCC>

The `.png` files listed in the `application.qrc` file are files that are part of the Application example's source tree. Paths are relative to the directory where the `application.qrc` file is located (the `mainwindows/application` directory).

The resource file must be mentioned in the `application.pro` file so that `qmake` knows about it:

     RESOURCES     = application.qrc

`qmake` will produce make rules to generate a file called `qrc_application.cpp` that is linked into the application. This file contains all the data for the images and other resources as static C++ arrays of compressed binary data. See The Qt Resource System for more information about resources.

Example project @ code.qt.io