1
2@c %start of fragment
3
4@node GtkActionGroup
5@chapter GtkActionGroup
6A group of actions
7
8@section Overview
9Actions are organised into groups. An action group is essentially a map from
10names to @code{<gtk-action>} objects.
11
12All actions that would make sense to use in a particular context should be in a
13single group. Multiple action groups may be used for a particular user
14interface. In fact, it is expected that most nontrivial applications will make
15use of multiple groups. For example, in an application that can edit multiple
16documents, one group holding global actions (e.g. quit, about, new), and one
17group per document holding actions that act on that document (eg. save,
18cut/copy/paste, etc). Each window's menus would be constructed from a
19combination of two action groups.
20
21Accelerators are handled by the GTK+ accelerator map. All actions are assigned
22an accelerator path (which normally has the form @samp{<Actions>//}) and a
23shortcut is associated with this accelerator path. All menuitems and toolitems
24take on this accelerator path. The GTK+ accelerator map code makes sure that the
25correct shortcut is displayed next to the menu item.
26
27@section Usage
28@include defuns-gtkactiongroup.xml.texi
29
30@c %end of fragment
31