Interface

GstPbutils-1.0 ▶ GstPbutils ▶ Discoverer ▶ SignalSignatures

interface SignalSignatures {
    discovered: (arg0: GstPbutils.DiscovererInfo, arg1: GLib.Error) => void;
    finished: () => void;
    "load-serialized-info": (arg0: string) => GstPbutils.DiscovererInfo;
    notify: (arg0: GObject.ParamSpec) => void;
    "notify::timeout": (pspec: GObject.ParamSpec) => void;
    "notify::use-cache": (pspec: GObject.ParamSpec) => void;
    "source-setup": (arg0: Gst.Element) => void;
    starting: () => void;
}

Hierarchy (View Summary)

Index

Properties

discovered finished load-serialized-info notify::timeout notify::use-cache source-setup starting

Properties - Inherited from GObject

notify

Properties

discovered: (arg0: GstPbutils.DiscovererInfo, arg1: GLib.Error) => void

Will be emitted in async mode when all information on a URI could be discovered, or an error occurred.

When an error occurs, info might still contain some partial information, depending on the circumstances of the error.

finished: () => void

Will be emitted in async mode when all pending URIs have been processed.

"load-serialized-info": (arg0: string) => GstPbutils.DiscovererInfo

Retrieves information about a URI from and external source of information, like a cache file. This is used by the discoverer to speed up the discovery.

1.24

"notify::timeout": (pspec: GObject.ParamSpec) => void
"notify::use-cache": (pspec: GObject.ParamSpec) => void
"source-setup": (arg0: Gst.Element) => void

This signal is emitted after the source element has been created for, so the URI being discovered, so it can be configured by setting additional properties (e.g. set a proxy server for an http source, or set the device and read speed for an audio cd source).

This signal is usually emitted from the context of a GStreamer streaming thread.

starting: () => void

Will be emitted when the discover starts analyzing the pending URIs

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.