SignalRun Lastload-SignalRun Lastunload-The unload-plugin signal is emitted when a plugin is being unloaded.
The plugin is being unloaded in the default handler. Hence, if you want to perform some action before the plugin is unloaded (the most common case), you should use GObject.signal_connect, but if you want to perform some action after the plugin is unloaded (the most common case), you should use GObject.signal_connect_after.
SignalDetailedActionRun FirstnotifyThe 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.
The load-plugin signal is emitted when a plugin is being loaded.
The plugin is being loaded in the default handler. Hence, if you want to perform some action before the plugin is loaded, you should use GObject.signal_connect, but if you want to perform some action after the plugin is loaded (the most common case), you should use GObject.signal_connect_after.