:right-sidebar: True

DBusActionGroup
===================================================================

.. currentmodule:: gi.repository.Gio





.. class:: DBusActionGroup(**properties: ~typing.Any)
   :no-contents-entry:


Superclasses: :class:`~gi.repository.GObject.Object`



Implemented Interfaces: :class:`~gi.repository.Gio.ActionGroup`, :class:`~gi.repository.Gio.RemoteActionGroup`



:Constructors:

::

    DBusActionGroup(**properties)





Methods
-------

.. rst-class:: interim-class

.. class:: DBusActionGroup
   :no-index:


   .. method:: get(connection: ~gi.repository.Gio.DBusConnection, bus_name: str | None, object_path: str) -> ~gi.repository.Gio.DBusActionGroup

      Obtains a :obj:`~gi.repository.Gio.DBusActionGroup` for 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
      :func:`~gi.repository.Gio.ActionGroup.list_actions` to get the initial list.



      .. versionadded:: 2.32





      :param connection: A :obj:`~gi.repository.Gio.DBusConnection`


      :param bus_name: the bus name which exports the action
         group or :const:`None` if ``connection`` is not a message bus connection


      :param object_path: the object path at which the action group is exported