Interface

Gdk-3.0 ▶ Gdk ▶ FrameClock ▶ SignalSignatures

interface SignalSignatures {
    "after-paint": () => void;
    "before-paint": () => void;
    "flush-events": () => void;
    layout: () => void;
    notify: (arg0: GObject.ParamSpec) => void;
    paint: () => void;
    "resume-events": () => void;
    update: () => void;
}

Hierarchy (View Summary)

Index

Properties

after-paint before-paint flush-events layout paint resume-events update

Properties - Inherited from GObject

notify

Properties

"after-paint": () => void

This signal ends processing of the frame. Applications should generally not handle this signal.

"before-paint": () => void

This signal begins processing of the frame. Applications should generally not handle this signal.

"flush-events": () => void

This signal is used to flush pending motion events that are being batched up and compressed together. Applications should not handle this signal.

layout: () => void

This signal is emitted as the second step of toolkit and application processing of the frame. Any work to update sizes and positions of application elements should be performed. GTK+ normally handles this internally.

paint: () => void

This signal is emitted as the third step of toolkit and application processing of the frame. The frame is repainted. GDK normally handles this internally and produces expose events, which are turned into GTK+ GtkWidget::draw signals.

"resume-events": () => void

This signal is emitted after processing of the frame is finished, and is handled internally by GTK+ to resume normal event processing. Applications should not handle this signal.

update: () => void

This signal is emitted as the first step of toolkit and application processing of the frame. Animations should be updated using gdk_frame_clock_get_frame_time(). Applications can connect directly to this signal, or use gtk_widget_add_tick_callback() as a more convenient interface.

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.