From 435b2418dae32a5d5e5ee750744e4061d1cf07b8 Mon Sep 17 00:00:00 2001 From: Matthias Clasen Date: Sat, 26 Nov 2011 21:44:46 -0500 Subject: [PATCH] GActionGroup: Mention GMenuModel in the docs --- gio/gactiongroup.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/gio/gactiongroup.c b/gio/gactiongroup.c index 7352ec1..7559fb3 100644 --- a/gio/gactiongroup.c +++ b/gio/gactiongroup.c @@ -35,12 +35,15 @@ * method calls, except g_action_group_list_actions() take the name of * an action as an argument. * + * Action groups are often used together with a #GMenuModel that provides + * additional representation data for the actions. + * * The #GActionGroup API is meant to be the 'public' API to the action * group. The calls here are exactly the interaction that 'external * forces' (eg: UI, incoming D-Bus messages, etc.) are supposed to have * with actions. 'Internal' APIs (ie: ones meant only to be accessed by * the action group implementation) are found on subclasses. This is - * why you will find -- for example -- g_action_group_get_action_enabled() + * why you will find - for example - g_action_group_get_action_enabled() * but not an equivalent set() call. * * Signals are emitted on the action group in response to state changes @@ -49,7 +52,7 @@ * Implementations of #GActionGroup should provide implementations for * the virtual functions g_action_group_list_actions() and * g_action_group_query_action(). The other virtual functions should - * not be implemented -- their "wrappers" are actually implemented with + * not be implemented - their "wrappers" are actually implemented with * calls to g_action_group_query_action(). **/ -- 2.7.4