Gio.DBusActionGroup¶
| Subclasses: | None | 
|---|
Methods¶
| Inherited: | GObject.Object (37), Gio.ActionGroup (14), Gio.RemoteActionGroup (2) | 
|---|---|
| Structs: | GObject.ObjectClass (5) | 
| class | get(connection, bus_name, object_path) | 
Virtual Methods¶
| Inherited: | GObject.Object (7), Gio.ActionGroup (14), Gio.RemoteActionGroup (2) | 
|---|
Properties¶
None
Signals¶
| Inherited: | GObject.Object (1), Gio.ActionGroup (4) | 
|---|
Fields¶
| Inherited: | GObject.Object (1), Gio.ActionGroup (4) | 
|---|
Class Details¶
- 
class Gio.DBusActionGroup(**kwargs)¶
- Bases: - GObject.Object,- Gio.ActionGroup,- Gio.RemoteActionGroup- Abstract: - No - Gio.DBusActionGroupis an implementation of the- Gio.ActionGroupinterface that can be used as a proxy for an action group that is exported over D-Bus with- Gio.DBusConnection.export_action_group().- 
classmethod get(connection, bus_name, object_path)[source]¶
- Parameters: - connection (Gio.DBusConnection) – AGio.DBusConnection
- bus_name (strorNone) – the bus name which exports the action group orNoneif connection is not a message bus connection
- object_path (str) – the object path at which the action group is exported
 - Returns: - Return type: - Obtains a - Gio.DBusActionGroupfor the action group which is exported at the given bus_name and object_path.- The thread default main context is taken at the time of this call. All signals on the menu model (and any linked models) are reported with respect to this context. All calls on the returned menu model (and linked models) must also originate from this same context, with the thread default main context unchanged. - This call is non-blocking. The returned action group may or may not already be filled in. The correct thing to do is connect the signals for the action group to monitor for changes and then to call - Gio.ActionGroup.list_actions() to get the initial list.- New in version 2.32. 
- connection (
 
- 
classmethod