GTK and GLib have a powerful API called GLib.Action which can be used to define the primary actions of your app, assign them keyboard shortcuts, and tie them to Actionable widgets in your app like Buttons and Menu Items. In this section, we're going to create a Quit action for your app with an assigned keyboard shortcut and a Button that shows that shortcut in a tooltip.

Gtk.HeaderBar

Begin by creating a Gtk.Application with a Gtk.ApplicationWindow as you've done in previous examples. Once you have that set up, let's create a new Gtk.HeaderBar. Typically your app will have a HeaderBar, at the top of the window, which will contain tool items that users will interact with to trigger your app's actions.

protected override void activate () {
    var header_bar = new Gtk.HeaderBar () {
        show_close_button = true
    };
​
    var main_window = new Gtk.ApplicationWindow (this) {
        default_height = 300,
        default_width = 300,
        title = "Actions"
    };
    main_window.set_titlebar (header_bar);
    main_window.show_all ();
}

Since we're using this HeaderBar as our app's main titlebar, we need to set show_close_button to true so that GTK knows to include window controls. We can then override our Window's built-in titlebar with the set_titlebar () method.

Now, still in the activate function, let's create a new Gtk.Button with a big colorful icon and add it to our headerbar:

protected override void activate () {
    var button = new Gtk.Button.from_icon_name ("process-stop", Gtk.IconSize.LARGE_TOOLBAR);
​
    var header_bar = new Gtk.HeaderBar () {
        show_close_button = true
    };
    header_bar.add (button);
​
    [...]
}

If you compile your app, you can see that it now has a custom HeaderBar with a big red icon in it. But when you click on it, nothing happens.

GLib.SimpleAction

Let's define a new Quit action by adding the following to the beginning of the activate () method

var quit_action = new SimpleAction ("quit", null);
​
add_action (quit_action);
set_accels_for_action ("app.quit",  {"<Control>q", "<Control>w"});

and this to the end of the activate () method:

quit_action.activate.connect (() => {
    main_window.destroy ();
});

You'll notice that we do a few things here:

• Instantiate a new GLib.SimpleAction with the name "quit"

• Add the action to our Gtk.Application's ActionMap​

• Set the "accelerators" (keyboard shortcuts) for "app.quit" to <Control>q and <Control>w". Notice that the action name is prefixed with app; this refers to the ActionMap built in to Gtk.Application

• Connect to the activate signal of our SimpleAction and call destroy () on main_window. This must be at the end of activate () because of that reference to main_window

and now we can tie the action to the HeaderBar Button by assigning the action_name property of our Button:

var button = new Gtk.Button.from_icon_name ("process-stop", Gtk.IconSize.LARGE_TOOLBAR) {
    action_name = "app.quit"
};

Compile your app again and see that you can now quit the app either through the defined keyboard shortcuts or by clicking the Button in the HeaderBar.

Granite.markup_accel_tooltip

There's one more thing we can do here to help improve your app's usability. You may have noticed that in elementary apps you can hover your pointer over tool items to see a description of the button and any available keyboard shortcuts associated with it. We can add the same thing to our Button with Granite.markup_accel_tooltip ().

First, make sure you've included Granite in the build dependencies declared in your meson.build file:

executable(
    meson.project_name(),
    'src/Application.vala',
    dependencies: [
        dependency('granite'),
        dependency('gtk+-3.0')
    ],
    install: true
)

Then, set the tooltip_markup property of your HeaderBar Button:

var button = new Gtk.Button.from_icon_name ("process-stop", Gtk.IconSize.LARGE_TOOLBAR) {
    action_name = "app.quit",
    tooltip_markup = Granite.markup_accel_tooltip (
        get_accels_for_action ("app.quit"),
        "Quit"
    )
};

It may now be clear why we needed to declare our action at the beginning of activate (): before we can get a list of the accelerators associated with the action, we have to define those accelerations and add them to the Application.

Compile your app one last time and hover over the HeaderBar Button to see its description and associated keyboard shortcuts.