Nova Flow OS
KDE Developer Platform
KDE Developer Platform
  • KDE Developer Platform
    • Getting started
      • Building KDE software
        • KDE software
        • Where to find the development team
        • Learning more
        • Choose what to work on
        • Source code cross-referencing
        • Installing build dependencies
        • Set up a development environment
        • Building KDE software with kdesrc-build
        • Basic troubleshooting
        • Tips and tricks
        • IDE Configuration
          • Setting up an IDE for KDE development
          • Visual Studio Code
          • Qt Creator
          • Kate
          • KDevelop
          • CLion
          • Sublime Text
        • Building KDE software manually
        • Building KDE software with distrobox and podman
      • Kirigami
        • KDE is ours
        • Setting up and getting started
        • Explaining pages
        • Layouts, ListViews, and Cards
        • Adding actions
        • Adding a dialog
        • Using separate files
        • Next steps
        • Colors and themes in Kirigami
        • Typography
        • Actions based components
        • Page rows and page stacks
        • Scrollable pages and list views
        • Cards
        • Drawers
        • Chips
        • Dialog types
        • Controls and interactive elements
        • Form layouts
        • Inline messages
        • Action toolbars
        • Progress bars and indicators
        • List views
        • Understanding CMakeLists
        • Figuring out main.cpp
        • Connect logic to your QML user interface
        • Connect models to your QML user interface
        • About page
        • Introduction to Kirigami Addons
        • FormCard About pages
        • Form delegates in your settings pages
      • KXmlGui
        • Getting started with KXmlGui
        • Hello World!
        • Creating the main window
        • Using actions
        • Saving and loading
        • Command line interface
      • Python with Kirigami
        • Apps with QML and Python
        • Your first Python + Kirigami application
        • Creating a Python package
        • Creating a Flatpak
      • Common programming mistakes
      • Adding a new KDE project
    • Features
      • Icons
      • Configuration
        • The KConfig Framework
        • Introduction to KConfig
        • Using KConfig XT
        • KDE Frameworks 6 porting guide
        • Settings module (KCM) development
        • KConfigDialog
      • D-Bus
        • What is D-Bus practically useful for?
        • Introduction to D-Bus
        • Accessing D-Bus interfaces
        • Intermediate D-Bus
        • Creating D-Bus interfaces
        • Using custom types with D-Bus
        • D-Bus autostart services
      • Create your own mouse cursor theme
      • Session management
      • Archives
      • Desktop file
      • KAuth
        • Privilege Escalation
        • Using actions in your applications
      • KIdleTime
      • Akonadi: personal information management
        • Debugging Akonadi Resources
        • Using Akonadi in applications
      • Concurrent programming
      • Solid
      • Sonnet
    • Plasma themes and plugins
      • Getting started
      • Plasma Widget tutorial
        • How to create a plasmoid
        • Setup
        • Porting Plasmoids to KF6
        • Testing
        • QML
        • Plasma's QML API
        • Widget Properties
        • Configuration
        • Translations / i18n
        • Examples
        • C++ API
      • KWin Effects
      • Plasma Desktop scripting
        • Javascript Interaction With Plasma Shells
        • Templates
        • Examples
        • API documentation
        • Configuration keys
      • Plasma Style tutorial
        • Creating a Plasma Style quickstart
        • Understanding Plasma Styles
        • SVG elements and Inkscape
        • Background SVG format
        • System and accent colors
        • Theme elements reference
        • Porting themes to Plasma 5
        • Porting themes to Plasma 6
      • Aurorae window decorations
      • KWin scripting tutorial
        • Quick start
        • KWin scripting API
      • Wallpapers
      • Plasma comic
        • Tutorial
        • Testing and debugging
        • Examples
      • Create a custom Window Switcher
      • KRunner C++ Plugin
        • Basic Anatomy of a Runner
        • KRunner metadata format
    • Applications
      • Creating sensor faces
      • Dolphin
        • Creating Dolphin service menus
      • Kate
        • Kate plugin tutorial
      • KMines
        • Making a KMines theme
      • Writing tests
        • Appium automation testing
    • Packaging
      • Android
        • KDE on Android
        • Building applications for Android
        • Packaging and publishing applications for Android
        • Publishing on Google Play
          • Introduction
          • Packaging your app
          • Adding your app to Google Play
          • Publishing your app
          • Releasing new versions of old apps
        • Porting applications to Android
          • Basic porting
          • Making applications run well on Android
          • Metadata
      • Windows
        • Packaging and publishing applications for Windows
        • Publish your app in the Microsoft Store
          • Packaging your app for the Microsoft Store
          • Submitting your app to the Microsoft Store
      • Plasma Mobile
        • KDE on mobile devices
        • Porting a new device to Plasma Mobile
        • KDE Telephony stack
          • General Overview
          • Kernel layer
          • System daemons
            • General overview
            • Developing Telephony functionality
            • ModemManager Telephony functions
          • Session daemons
          • QML declarative plugin layer
          • KDE application layer
        • Execute applications
      • Distributing KDE software as Flatpak
        • Your first Flatpak
        • Extending your package
        • Nightly Flatpaks and Flathub
        • Testing your Flatpak
    • System administration
      • Shell scripting with KDE dialogs
      • Kiosk: Simple configuration management for large deployment
        • Abstract
        • Introduction to Kiosk
        • Kiosk keys
    • Contribute to the documentation
    • About
      • Readme
      • License
        • Creative Commons Attribution-ShareAlike 4.0 International
        • GNU General Public License 3.0 or later
Powered by GitBook
On this page
  • Introduction
  • QActions
  • The Code
  • Explanation
  • CMake
  • Running our application
  1. KDE Developer Platform
  2. Getting started
  3. KXmlGui

Using actions

How to add actions to the menus and toolbars.

PreviousCreating the main windowNextSaving and loading

Last updated 8 months ago

Introduction

This tutorial introduces the concept of actions. Actions are a unified way of supplying the user with ways to interact with your program.

For example, if we wanted to let the user of our clear the text box by clicking a button in the toolbar, from an option in the File menu or through a keyboard shortcut, it could all be done with one .

QActions

The Code

main.cpp

We are going to install our UI .rc file under the component texteditor, so main.cpp should be changed to reflect that change in name.

Don't worry about the .rc file just yet. We will see what it's about by the end of this tutorial.

    // ...
    KLocalizedString::setApplicationDomain("texteditor");

    KAboutData aboutData(
            u"texteditor"_s,
    // ...

mainwindow.h

#ifndef MAINWINDOW_H
#define MAINWINDOW_H

#include <KXmlGuiWindow>

class KTextEdit;

class MainWindow : public KXmlGuiWindow
{
public:
    explicit MainWindow(QWidget *parent = nullptr);

private:
    KTextEdit *textArea;
    void setupActions();
};

#endif // MAINWINDOW_H

mainwindow.cpp

#include <QApplication>
#include <QAction>
#include <KTextEdit>
#include <KLocalizedString>
#include <KActionCollection>
#include <KStandardAction>
#include "mainwindow.h"

MainWindow::MainWindow(QWidget *parent) : KXmlGuiWindow(parent)
{
    textArea = new KTextEdit();
    setCentralWidget(textArea);
    setupActions();
}

void MainWindow::setupActions()
{
    using namespace Qt::Literals::StringLiterals;

    QAction *clearAction = new QAction(this);
    clearAction->setText(i18n("&Clear"));
    clearAction->setIcon(QIcon::fromTheme(u"document-new-symbolic"_s));
    actionCollection()->addAction(u"clear"_s, clearAction);
    actionCollection()->setDefaultShortcut(clearAction, Qt::CTRL | Qt::Key_L);
    connect(clearAction, &QAction::triggered, textArea, &KTextEdit::clear);

    KStandardAction::quit(qApp, &QCoreApplication::quit, actionCollection());

    setupGUI(Default, u"texteditorui.rc"_s);
}

Explanation

Creating the QAction object

#include <QAction>
...
QAction *clearAction = new QAction(this);

Setting QAction Properties

clearAction->setText(i18n("&Clear"));

The ampersand (&) in the action text denotes which letter will be used as an accelerator for said action. If the user opens a menu and presses the 'Alt' key, this will highlight the first letter of 'Clear' with an underscore, denoting the key they can press to perform said action. In this case, the user would press 'Alt+C' to clear the textbox when the File menu is open.

The ampersand is also useful for internationalisation: in non-Latin languages such as Japanese (where 'copy' is コピー), using the first letter of that language to accelerate the action could be cumbersome. The ampersand lets translators know whether they should include the Latin character in parentheses, allowing non-English users to use the same accelerator key even if the translated string is completely different.

Icon

clearAction->setIcon(QIcon::fromTheme(u"document-new-symbolic"_s));

Adding to the Collection

The action collection is accessed via the actionCollection() function like this:

actionCollection()->addAction("clear", clearAction);

Keyboard Shortcuts

actionCollection()->setDefaultShortcut(clearAction, Qt::CTRL + Qt::Key_W);

Connecting the action

connect(clearAction, &QAction::triggered, textArea, &KTextEdit::clear);

KStandardAction

They are very simple to use. Once the library has been included (#include <KStandardAction>), simply supply it with what you want the function to do and which QActionCollection to add it to. For example:

KStandardAction::quit(qApp, &QCoreApplication::quit, actionCollection());

In the end, this creates an action with the correct icon, text and shortcut and even adds it to the File menu.

Adding the action to menus and toolbars

Defining your own help menu

XMLGUI

appnameui.rc file

Since the description of the UI is defined with XML, the layout must follow strict rules. This tutorial will not go into great depth on this topic.

texteditorui.rc

<?xml version="1.0" encoding="UTF-8"?>
<gui name="texteditor"
     version="1"
     xmlns="https://www.kde.org/standards/kxmlgui/1.0"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="https://www.kde.org/standards/kxmlgui/1.0
                         https://www.kde.org/standards/kxmlgui/1.0/kxmlgui.xsd">
  <MenuBar>
    <Menu name="file" >
      <Action name="clear" />
    </Menu>
    <Menu >
      <text>A&amp;nother Menu</text>
      <Action name="clear" />
    </Menu>
  </MenuBar>

  <ToolBar name="mainToolBar" >
    <text>Main Toolbar</text>
    <Action name="clear" />
  </ToolBar>
</gui>

Besides having the action in the toolbar, it can also be added to the menubar. Here the action is being added to the File menu of the MenuBar the same way it was added to the toolbar.

Change the 'version' attribute of the <gui> tag if you changed the .rc file since the last install to force a system cache update. Be sure it is an integer, if you use a decimal value, it will not work, and you will get no warning about it.

Warning The version attribute must always be an integer number.

Some notes on the interaction between code and the .rc file: menus appear automatically and should have a <text/> child tag unless they refer to standard menus. Actions need to be created manually and inserted into the actionCollection() using the same name as in the .rc file. Actions can be hidden or disabled, whereas menus can't.

CMake

Finally, the texteditorui.rc needs to go somewhere where the system can find it (you can't just leave it in the source directory!). This means the project needs to be installed somewhere, unlike in the previous tutorials.

CMakeLists.txt

cmake_minimum_required(VERSION 3.20)

project(texteditor)

set(QT_MIN_VERSION "6.6.0")
set(KF_MIN_VERSION "6.0.0")

find_package(ECM ${KF_MIN_VERSION} REQUIRED NO_MODULE)
set(CMAKE_MODULE_PATH ${ECM_MODULE_PATH} ${CMAKE_CURRENT_SOURCE_DIR}/cmake)

include(KDEInstallDirs)
include(KDECMakeSettings)
include(KDECompilerSettings NO_POLICY_SCOPE)
include(FeatureSummary)

find_package(Qt6 ${QT_MIN_VERSION} CONFIG REQUIRED COMPONENTS
    Core    # QCommandLineParser, QStringLiteral
    Widgets # QApplication, QAction
)

find_package(KF6 ${KF_MIN_VERSION} REQUIRED COMPONENTS
    CoreAddons      # KAboutData
    I18n            # KLocalizedString
    XmlGui          # KXmlGuiWindow, KActionCollection
    TextWidgets     # KTextEdit
    ConfigWidgets   # KStandardActions
)

add_executable(texteditor)

target_sources(texteditor
    PRIVATE
    main.cpp
    mainwindow.cpp
)

target_link_libraries(texteditor
    Qt6::Widgets
    KF6::CoreAddons
    KF6::I18n
    KF6::XmlGui
    KF6::TextWidgets
    KF6::ConfigWidgets
)

install(TARGETS texteditor ${KDE_INSTALL_TARGETS_DEFAULT_ARGS})
install(FILES texteditorui.rc DESTINATION ${KDE_INSTALL_KXMLGUIDIR}/texteditor)

feature_summary(WHAT ALL INCLUDE_QUIET_PACKAGES FATAL_ON_MISSING_REQUIRED_PACKAGES)

This file is almost identical to the one for the [previous tutorial]({{< relref "main_window/#cmakeliststxt" >}}), but with two extra lines at the end that describe where the files are to be installed. Firstly, the texteditor target is installed to the right place for binaries using ${KDE_INSTALL_TARGETS_DEFAULT_ARGS}, then the texteditorui.rc file that describes the layout of the user interface is installed to the application's data directory, ${KDE_INSTALL_KXMLGUIDIR}.

Running our application

You can repeat the same steps provided in {{< ref "hello_world#kxmlgui-running" >}} to build and install the application. You can then run the project with:

kdesrc-build --run --exec mainwindow kxmlgui-tutorial

or

mainwindow

As you might remember from the [KXmlGui Hello World]{{< ref "hello_world" >}}, when installing the project manually with CMake, we specified the --prefix flag:

cmake --install build/ --prefix "~/.local"

This will create a /usr-like directory structure in ~/.local. Specifically, it will create the directories $HOME/.local/bin/ and $HOME/.local/share/, then install the executable to $HOME/.local/bin/texteditor and the texteditorui.rc file to $HOME/.local/share/kxmlgui/texteditor/texteditorui.rc.

A is an object which contains all the information about the icon and shortcuts that are associated with a certain action. With the use of , whenever that action is triggered (like clicking a menu option), a function in a different part of your program is automatically run.

are most commonly used in shown in a , a , or in a right click context menu.

Only a function void setupActions() has been added which will do all the work setting up the .

This builds upon the code from our previous [main window]({{< ref "main_window.md" >}}). Most of the changes are to mainwindow.cpp, an important structural change being that the constructor for MainWindow now calls setupActions() instead of setupGUI(). setupActions() is where the new code goes before finally calling setupGUI() itself.

The QAction is built up in a number of steps. The first is including the header and then creating one:

This creates a new called clearAction.

Now that we have our object, we can start setting its properties. With , we can set the text that will be displayed in the menu and with an optional in the toolbar, depending on the widget style (whether beside or below the icon) or setting (whether to display the action text or not).

Note that the text is passed through the i18n() function; this is necessary for the UI to be translatable, as mentioned in [Hello World]({{< relref "hello_world/#about-and-internationalization" >}}) (more information on this can be found in the ).

If the action is going to be displayed in a toolbar, it is nice to have an icon depicting the action. The icon may also be displayed beside the action in the menus, depending on the widget style. We use a to grab the system's default icon for "document-new-symbolic" and use to assign it to our clearAction.

In order for the action to be accessed via (explained in depth later) it must be added to the application's action collection.

Because our uses the interface, we can use the utility virtual function to retrieve the list of actions in our application, returning a .

Because of the actionCollection()'s return type, we can use convenience functions made available via , like .

Here, our clearAction is added to the collection and given a name of clear. This name (clear) is used by the framework to refer to the action, so it is used internally and will not be localized.

We can then use one of the utility functions of our action collection, , to attribute a default keyboard shortcut of Ctrl+W:

The list of available keys can be found in the .

Now that the action is fully set up, it needs to be connected to something useful. In this case (because we want to clear the text area), we connect our action to the slot belonging to a (which, unsurprisingly, clears the text):

Here we are using a , Qt's most useful magic. The first parameter is the object we created and which sends the signal, our clearAction; the second is a reference to the signal itself, namely triggered(); the third is the object whose slot will receive the signal, our textArea; and the last one is a reference to the slot to receive the signal, namely clear(). In other words, this can be read as "connect this object's signal to that object's slot", or "when this signal fires, run that slot".

Refer to Qt's documentation on to understand this better. Signals and slots are essential to make Qt apps, understanding them is highly recommended.

For actions which would likely appear in almost every KDE application such as 'quit', 'save', and 'load' there are pre-created convenience , accessed through .

Here we call the method whenever is triggered. We are able to access that method via the macro, which returns a pointer to the specific object used in our application, the one in main().

At the moment, the new "Clear" action has been created but it hasn't been associated with any menus or toolbars. We will be using capabilities for that, as it does nice things like create movable toolbars for you.

The Help menu has been standardized to ease the lives of both developers and users, which is why all KDE software Help menus look the same. If you want to create your own help menu, you should refer to the explanation provided in the Using your own "about application" dialog box section of .

The setupGUI() function in depends on the system to construct the GUI, which is done by parsing an XML file description of the interface.

The rule for naming this XML file is appnameui.rc, where appname is the name you set in (in this case, TextEditor). So in our example, the file is called texteditorui.rc, and is placed in the same folder as our other files. Where the file will ultimately be placed is handled by CMake.

The <Toolbar> tag allows you to describe the toolbar, which is the bar across the top of the window normally with icons. Here it is given the unique name mainToolBar and its user visible name set to "Main Toolbar" using the <text> tag. The clear action is added to the toolbar using the <Action> tag, the name parameter in this tag being the string that was passed to the action collection with in mainwindow.cpp.

QAction
signals and slots
QActions
QMenus
QMenuBar
QToolBar
QActions
KXmlGuiWindow
QAction
QAction
QAction
QAction
QAction::setText()
QAction::icon()
internationalisation docs
QIcon::fromTheme()
QAction::setIcon()
KXmlGui
KXmlGuiWindow
KXmlGuiClient
KXmlGuiClient::actionCollection()
KActionCollection
KActionCollection
KActionCollection::addAction()
QAction
KXmlGui
KActionCollection::setDefaultShortcut()
Qt namespace Key enum
KTextEdit::clear()
KTextEdit
QObject::connect()
Signals and Slots
QActions
KStandardAction
QApplication::quit()
KStandardAction::quit()
QApplication::qApp
QApplication
KXmlGui's
KHelpMenu
KXmlGuiWindow
KXmlGui
KAboutData
KActionCollection::addAction()
main window tutorial
QAction