Gio-2.0 ▶ Gio ▶ NativeVolumeMonitor ▶ SignalSignatures

Emitted when a drive changes.

Emitted when a drive is connected to the system.

Emitted when a drive is disconnected from the system.

Emitted when the eject button is pressed on drive.

Emitted when the stop button is pressed on drive.

Emitted when a mount is added.

Emitted when a mount changes.

May be emitted when a mount is about to be removed.

This signal depends on the backend and is only emitted if GIO was used to unmount.

Emitted when a mount is removed.

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)
Copy

It is important to note that you must use [canonical parameter names][class@GObject.ParamSpec#parameter-names] as detail strings for the notify signal.

Emitted when a mountable volume is added to the system.

Emitted when mountable volume is changed.

Emitted when a mountable volume is removed from the system.