Interface

Gio-2.0 ▶ Gio ▶ DBusServer ▶ SignalSignatures

interface SignalSignatures {
    "new-connection": (arg0: Gio.DBusConnection) => boolean | void;
    notify: (arg0: GObject.ParamSpec) => void;
    "notify::active": (pspec: GObject.ParamSpec) => void;
    "notify::address": (pspec: GObject.ParamSpec) => void;
    "notify::authentication-observer": (pspec: GObject.ParamSpec) => void;
    "notify::client-address": (pspec: GObject.ParamSpec) => void;
    "notify::flags": (pspec: GObject.ParamSpec) => void;
    "notify::guid": (pspec: GObject.ParamSpec) => void;
}

Hierarchy (View Summary)

Index

Properties

new-connection notify::active notify::address notify::authentication-observer notify::client-address notify::flags notify::guid

Properties - Inherited from GObject

notify

Properties

"new-connection": (arg0: Gio.DBusConnection) => boolean | void

Emitted when a new authenticated connection has been made. Use g_dbus_connection_get_peer_credentials() to figure out what identity (if any), was authenticated.

If you want to accept the connection, take a reference to the connection object and return true. When you are done with the connection call g_dbus_connection_close() and give up your reference. Note that the other peer may disconnect at any time - a typical thing to do when accepting a connection is to listen to the Gio.DBusConnection::closed signal.

If Gio.DBusServer.flags contains Gio.DBusServerFlags.RUN_IN_THREAD then the signal is emitted in a new thread dedicated to the connection. Otherwise the signal is emitted in the thread-default main context (see GLib.MainContext.push_thread_default) of the thread that server was constructed in.

You are guaranteed that signal handlers for this signal runs before incoming messages on connection are processed. This means that it's suitable to call g_dbus_connection_register_object() or similar from the signal handler.

2.26

"notify::active": (pspec: GObject.ParamSpec) => void
"notify::address": (pspec: GObject.ParamSpec) => void
"notify::authentication-observer": (pspec: GObject.ParamSpec) => void
"notify::client-address": (pspec: GObject.ParamSpec) => void
"notify::flags": (pspec: GObject.ParamSpec) => void
"notify::guid": (pspec: GObject.ParamSpec) => void

Properties - Inherited from GObject

notify: (arg0: GObject.ParamSpec) => void

The notify signal is emitted on an object when one of its properties has its value set through g_object_set_property(), g_object_set(), et al.

Note that getting this signal doesn’t itself guarantee that the value of the property has actually changed. When it is emitted is determined by the derived GObject class. If the implementor did not create the property with GObject.ParamFlags.EXPLICIT_NOTIFY, then any call to g_object_set_property() results in ::notify being emitted, even if the new value is the same as the old. If they did pass GObject.ParamFlags.EXPLICIT_NOTIFY, then this signal is emitted only when they explicitly call g_object_notify() or g_object_notify_by_pspec(), and common practice is to do that only when the value has actually changed.

This signal is typically used to obtain change notification for a single property, by specifying the property name as a detail in the g_signal_connect() call, like this:

g_signal_connect (text_view->buffer, "notify::paste-target-list",
                  G_CALLBACK (gtk_text_view_target_list_notify),
                  text_view)

It is important to note that you must use [canonical parameter names][class@GObject.ParamSpec#parameter-names] as detail strings for the notify signal.