Interface

Gio-2.0 ▶ Gio ▶ SocketClient ▶ SignalSignatures

interface SignalSignatures {
    event: (
        arg0: Gio.SocketClientEvent,
        arg1: Gio.SocketConnectable,
        arg2: Gio.IOStream,
    ) => void;
    notify: (arg0: GObject.ParamSpec) => void;
    "notify::enable-proxy": (pspec: GObject.ParamSpec) => void;
    "notify::family": (pspec: GObject.ParamSpec) => void;
    "notify::local-address": (pspec: GObject.ParamSpec) => void;
    "notify::protocol": (pspec: GObject.ParamSpec) => void;
    "notify::proxy-resolver": (pspec: GObject.ParamSpec) => void;
    "notify::timeout": (pspec: GObject.ParamSpec) => void;
    "notify::tls": (pspec: GObject.ParamSpec) => void;
    "notify::tls-validation-flags": (pspec: GObject.ParamSpec) => void;
    "notify::type": (pspec: GObject.ParamSpec) => void;
}

Hierarchy (View Summary)

Index

Properties

event notify::enable-proxy notify::family notify::local-address notify::protocol notify::proxy-resolver notify::timeout notify::tls notify::tls-validation-flags notify::type

Properties - Inherited from GObject

notify

Properties

event: (
    arg0: Gio.SocketClientEvent,
    arg1: Gio.SocketConnectable,
    arg2: Gio.IOStream,
) => void

Emitted when client's activity on connectable changes state. Among other things, this can be used to provide progress information about a network connection in the UI. The meanings of the different event values are as follows:

Each event except Gio.SocketClientEvent.COMPLETE may be emitted multiple times (or not at all) for a given connectable (in particular, if client ends up attempting to connect to more than one address). However, if client emits the Gio.SocketClient::event signal at all for a given connectable, then it will always emit it with Gio.SocketClientEvent.COMPLETE when it is done.

Note that there may be additional Gio.SocketClientEvent values in the future; unrecognized event values should be ignored.

2.32

"notify::enable-proxy": (pspec: GObject.ParamSpec) => void
"notify::family": (pspec: GObject.ParamSpec) => void
"notify::local-address": (pspec: GObject.ParamSpec) => void
"notify::protocol": (pspec: GObject.ParamSpec) => void
"notify::proxy-resolver": (pspec: GObject.ParamSpec) => void
"notify::timeout": (pspec: GObject.ParamSpec) => void
"notify::tls": (pspec: GObject.ParamSpec) => void
"notify::tls-validation-flags": (pspec: GObject.ParamSpec) => void
"notify::type": (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.