Actions
Creating tool items, GLib.Actions, and keyboard shortcuts
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.1
protected override void activate () {
2
var header_bar = new Gtk.HeaderBar () {
3
show_close_button = true
4
};
5
6
var main_window = new Gtk.ApplicationWindow (this) {
7
default_height = 300,
8
default_width = 300,
9
title = "Actions"
10
};
11
main_window.set_titlebar (header_bar);
12
main_window.show_all ();
13
}
Copied!
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:1
protected override void activate () {
2
var button = new Gtk.Button.from_icon_name ("process-stop", Gtk.IconSize.LARGE_TOOLBAR);
3
4
var header_bar = new Gtk.HeaderBar () {
5
show_close_button = true
6
};
7
header_bar.add (button);
8
9
[...]
10
}
Copied!
elementary OS ships with a large set of system icons that you can use in your app for actions, status, and more. You can browse the full set of named icons using the app LookBook, available in AppCenter.
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 () method1
var quit_action = new SimpleAction ("quit", null);
2
3
add_action (quit_action);
4
set_accels_for_action ("app.quit", {"<Control>q", "<Control>w"});
Copied!
and this to the end of the
activate () method:1
quit_action.activate.connect (() => {
2
main_window.destroy ();
3
});
Copied!
You'll notice that we do a few things here:
- Set the "accelerators" (keyboard shortcuts) for "app.quit" to
<Control>qand<Control>w". Notice that the action name is prefixed withapp; this refers to theActionMapbuilt in toGtk.Application - Connect to the
activatesignal of ourSimpleActionand calldestroy ()onmain_window. This must be at the end ofactivate ()because of that reference tomain_window
and now we can tie the action to the HeaderBar Button by assigning the
action_name property of our Button:1
var button = new Gtk.Button.from_icon_name ("process-stop", Gtk.IconSize.LARGE_TOOLBAR) {
2
action_name = "app.quit"
3
};
Copied!
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.
Accelerator strings follow a format defined by
Gtk.accelerator_parse. You can find a list of key values on ValadocGranite.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:
1
executable(
2
meson.project_name(),
3
'src/Application.vala',
4
dependencies: [
5
dependency('granite'),
6
dependency('gtk+-3.0')
7
],
8
install: true
9
)
Copied!
Then, set the
tooltip_markup property of your HeaderBar Button:1
var button = new Gtk.Button.from_icon_name ("process-stop", Gtk.IconSize.LARGE_TOOLBAR) {
2
action_name = "app.quit",
3
tooltip_markup = Granite.markup_accel_tooltip (
4
get_accels_for_action ("app.quit"),
5
"Quit"
6
)
7
};
Copied!
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.
Last modified 6mo ago
Export as PDF
Copy link
Edit on GitHub