From 53a9b7f6c07209f287499127e3dfb65b3ba2065d Mon Sep 17 00:00:00 2001 From: Matthias Clasen Date: Wed, 3 Jun 2020 07:51:29 -0400 Subject: [PATCH] selection model: Further documentation tweaks Reword this to use plain language instead of throwing arond reentrancy and ordering. --- gtk/gtkselectionmodel.c | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/gtk/gtkselectionmodel.c b/gtk/gtkselectionmodel.c index b44b7cc0b0..8053368c6b 100644 --- a/gtk/gtkselectionmodel.c +++ b/gtk/gtkselectionmodel.c @@ -47,10 +47,9 @@ * If new items added to the model via the #GListModel::items-changed signal are selected * or not is up to the implementation. * - * Note that you need to listen to both #GListModel::items-changed and to - * #GtkSelectionModel::selection-changed to keep track of which items are selected. - * #GtkSelectionModel will generally only emit the one or the other signal, not - * both, to avoid ordering and reentrancy issues. + * Note that items added via #GListModel::items-changed may already be selected + * and no #GtkSelectionModel::selection-changed will be emitted for them. So to + * track which items are selected, it is necessary to listen to both signals. * * Additionally, the interface can expose functionality to select and unselect items. * If these functions are implemented, GTK's list widgets will allow users to select and