The places sidebar emits this signal when the user invokes a contextual
menu on one of its items. In the signal handler, the application may
add extra items to the menu as appropriate. For example, a file manager
may want to add a "Properties" command to the menu.
It is not necessary to store the @selected_item for each menu item;
during their GtkMenuItem::activate callbacks, the application can use
gtk_places_sidebar_get_location() to get the file to which the item
refers.
The @selected_item argument may be #NULL in case the selection refers to
a volume. In this case, @selected_volume will be non-NULL. In this case,
the calling application will have to g_object_ref() the @selected_volume and
keep it around for the purposes of its menu item's "activate" callback.
The @menu and all its menu items are destroyed after the user
dismisses the menu. The menu is re-created (and thus, this signal is
emitted) every time the user activates the contextual menu.
The places sidebar emits this signal when the user invokes a contextual menu on one of its items. In the signal handler, the application may add extra items to the menu as appropriate. For example, a file manager may want to add a "Properties" command to the menu.
It is not necessary to store the @selected_item for each menu item; during their GtkMenuItem::activate callbacks, the application can use gtk_places_sidebar_get_location() to get the file to which the item refers.
The @selected_item argument may be #NULL in case the selection refers to a volume. In this case, @selected_volume will be non-NULL. In this case, the calling application will have to g_object_ref() the @selected_volume and keep it around for the purposes of its menu item's "activate" callback.
The @menu and all its menu items are destroyed after the user dismisses the menu. The menu is re-created (and thus, this signal is emitted) every time the user activates the contextual menu.