Interface

Gio-2.0 ▶ Gio ▶ Settings ▶ SignalSignatures

interface SignalSignatures {
    "change-event": (arg0: number[]) => boolean | void;
    changed: (arg0: string) => void;
    "changed::backend": (arg0: string) => void;
    "changed::delay-apply": (arg0: string) => void;
    "changed::has-unapplied": (arg0: string) => void;
    "changed::path": (arg0: string) => void;
    "changed::schema": (arg0: string) => void;
    "changed::schema-id": (arg0: string) => void;
    "changed::settings-schema": (arg0: string) => void;
    notify: (arg0: GObject.ParamSpec) => void;
    "notify::backend": (pspec: GObject.ParamSpec) => void;
    "notify::delay-apply": (pspec: GObject.ParamSpec) => void;
    "notify::has-unapplied": (pspec: GObject.ParamSpec) => void;
    "notify::path": (pspec: GObject.ParamSpec) => void;
    "notify::schema": (pspec: GObject.ParamSpec) => void;
    "notify::schema-id": (pspec: GObject.ParamSpec) => void;
    "notify::settings-schema": (pspec: GObject.ParamSpec) => void;
    "writable-change-event": (arg0: number) => boolean | void;
    "writable-changed": (arg0: string) => void;
    "writable-changed::backend": (arg0: string) => void;
    "writable-changed::delay-apply": (arg0: string) => void;
    "writable-changed::has-unapplied": (arg0: string) => void;
    "writable-changed::path": (arg0: string) => void;
    "writable-changed::schema": (arg0: string) => void;
    "writable-changed::schema-id": (arg0: string) => void;
    "writable-changed::settings-schema": (arg0: string) => void;
}

Hierarchy (View Summary)

Index

Properties

change-event changed changed::backend changed::delay-apply changed::has-unapplied changed::path changed::schema changed::schema-id changed::settings-schema notify::backend notify::delay-apply notify::has-unapplied notify::path notify::schema notify::schema-id notify::settings-schema writable-change-event writable-changed writable-changed::backend writable-changed::delay-apply writable-changed::has-unapplied writable-changed::path writable-changed::schema writable-changed::schema-id writable-changed::settings-schema

Properties - Inherited from GObject

notify

Properties

"change-event": (arg0: number[]) => boolean | void

Emitted once per change event that affects this settings object.

You should connect to this signal only if you are interested in viewing groups of changes before they are split out into multiple emissions of the Gio.Settings::changed signal. For most use cases it is more appropriate to use the Gio.Settings::changed signal.

In the event that the change event applies to one or more specified keys, keys will be an array of GLib.Quarks of length n_keys. In the event that the change event applies to the Gio.Settings object as a whole (ie: potentially every key has been changed) then keys will be NULL and n_keys will be 0.

The default handler for this signal invokes the Gio.Settings::changed signal for each affected key. If any other connected handler returns true then this default functionality will be suppressed.

changed: (arg0: string) => void

Emitted when a key has potentially changed.

You should call one of the Gio.Settings.get calls to check the new value.

This signal supports detailed connections. You can connect to the detailed signal changed::x in order to only receive callbacks when key x changes.

Note that settings only emits this signal if you have read key at least once while a signal handler was already connected for key.

"changed::backend": (arg0: string) => void

Emitted when a key has potentially changed.

You should call one of the Gio.Settings.get calls to check the new value.

This signal supports detailed connections. You can connect to the detailed signal changed::x in order to only receive callbacks when key x changes.

Note that settings only emits this signal if you have read key at least once while a signal handler was already connected for key.

"changed::delay-apply": (arg0: string) => void

Emitted when a key has potentially changed.

You should call one of the Gio.Settings.get calls to check the new value.

This signal supports detailed connections. You can connect to the detailed signal changed::x in order to only receive callbacks when key x changes.

Note that settings only emits this signal if you have read key at least once while a signal handler was already connected for key.

"changed::has-unapplied": (arg0: string) => void

Emitted when a key has potentially changed.

You should call one of the Gio.Settings.get calls to check the new value.

This signal supports detailed connections. You can connect to the detailed signal changed::x in order to only receive callbacks when key x changes.

Note that settings only emits this signal if you have read key at least once while a signal handler was already connected for key.

"changed::path": (arg0: string) => void

Emitted when a key has potentially changed.

You should call one of the Gio.Settings.get calls to check the new value.

This signal supports detailed connections. You can connect to the detailed signal changed::x in order to only receive callbacks when key x changes.

Note that settings only emits this signal if you have read key at least once while a signal handler was already connected for key.

"changed::schema": (arg0: string) => void

Emitted when a key has potentially changed.

You should call one of the Gio.Settings.get calls to check the new value.

This signal supports detailed connections. You can connect to the detailed signal changed::x in order to only receive callbacks when key x changes.

Note that settings only emits this signal if you have read key at least once while a signal handler was already connected for key.

"changed::schema-id": (arg0: string) => void

Emitted when a key has potentially changed.

You should call one of the Gio.Settings.get calls to check the new value.

This signal supports detailed connections. You can connect to the detailed signal changed::x in order to only receive callbacks when key x changes.

Note that settings only emits this signal if you have read key at least once while a signal handler was already connected for key.

"changed::settings-schema": (arg0: string) => void

Emitted when a key has potentially changed.

You should call one of the Gio.Settings.get calls to check the new value.

This signal supports detailed connections. You can connect to the detailed signal changed::x in order to only receive callbacks when key x changes.

Note that settings only emits this signal if you have read key at least once while a signal handler was already connected for key.

"notify::backend": (pspec: GObject.ParamSpec) => void
"notify::delay-apply": (pspec: GObject.ParamSpec) => void
"notify::has-unapplied": (pspec: GObject.ParamSpec) => void
"notify::path": (pspec: GObject.ParamSpec) => void
"notify::schema": (pspec: GObject.ParamSpec) => void
"notify::schema-id": (pspec: GObject.ParamSpec) => void
"notify::settings-schema": (pspec: GObject.ParamSpec) => void
"writable-change-event": (arg0: number) => boolean | void

Emitted once per writability change event that affects this settings object.

You should connect to this signal if you are interested in viewing groups of changes before they are split out into multiple emissions of the Gio.Settings::writable-changed signal. For most use cases it is more appropriate to use the Gio.Settings::writable-changed signal.

In the event that the writability change applies only to a single key, key will be set to the GLib.Quark for that key. In the event that the writability change affects the entire settings object, key will be 0.

The default handler for this signal invokes the Gio.Settings::writable-changed and Gio.Settings::changed signals for each affected key. This is done because changes in writability might also imply changes in value (if for example, a new mandatory setting is introduced). If any other connected handler returns true then this default functionality will be suppressed.

"writable-changed": (arg0: string) => void

Emitted when the writability of a key has potentially changed.

You should call Gio.Settings.is_writable in order to determine the new status.

This signal supports detailed connections. You can connect to the detailed signal writable-changed::x in order to only receive callbacks when the writability of x changes.

"writable-changed::backend": (arg0: string) => void

Emitted when the writability of a key has potentially changed.

You should call Gio.Settings.is_writable in order to determine the new status.

This signal supports detailed connections. You can connect to the detailed signal writable-changed::x in order to only receive callbacks when the writability of x changes.

"writable-changed::delay-apply": (arg0: string) => void

Emitted when the writability of a key has potentially changed.

You should call Gio.Settings.is_writable in order to determine the new status.

This signal supports detailed connections. You can connect to the detailed signal writable-changed::x in order to only receive callbacks when the writability of x changes.

"writable-changed::has-unapplied": (arg0: string) => void

Emitted when the writability of a key has potentially changed.

You should call Gio.Settings.is_writable in order to determine the new status.

This signal supports detailed connections. You can connect to the detailed signal writable-changed::x in order to only receive callbacks when the writability of x changes.

"writable-changed::path": (arg0: string) => void

Emitted when the writability of a key has potentially changed.

You should call Gio.Settings.is_writable in order to determine the new status.

This signal supports detailed connections. You can connect to the detailed signal writable-changed::x in order to only receive callbacks when the writability of x changes.

"writable-changed::schema": (arg0: string) => void

Emitted when the writability of a key has potentially changed.

You should call Gio.Settings.is_writable in order to determine the new status.

This signal supports detailed connections. You can connect to the detailed signal writable-changed::x in order to only receive callbacks when the writability of x changes.

"writable-changed::schema-id": (arg0: string) => void

Emitted when the writability of a key has potentially changed.

You should call Gio.Settings.is_writable in order to determine the new status.

This signal supports detailed connections. You can connect to the detailed signal writable-changed::x in order to only receive callbacks when the writability of x changes.

"writable-changed::settings-schema": (arg0: string) => void

Emitted when the writability of a key has potentially changed.

You should call Gio.Settings.is_writable in order to determine the new status.

This signal supports detailed connections. You can connect to the detailed signal writable-changed::x in order to only receive callbacks when the writability of x changes.

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.