After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 749252 - GtkListBox don’t deselect entries if ‘selection-mode’ is GTK_SELECTION_MODE_MULTIPLE
GtkListBox don’t deselect entries if ‘selection-mode’ is GTK_SELECTION_MODE_M...
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: Other
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2015-05-12 07:05 UTC by Marcus Habermehl (BMH1980)
Modified: 2018-05-02 16:34 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
A glade file demonstrating the bug (2.48 KB, application/x-glade)
2018-02-11 19:34 UTC, Christian Stadelmann
Details

Description Marcus Habermehl (BMH1980) 2015-05-12 07:05:56 UTC
If I set the property ‘activate-on-single-click’ to TRUE and ‘selection-mode’ to GTK_SELECTION_MODE_MULTIPLE children can’t be deselected with a click.

By clicking on an unselected row the signals ‘row-selected’, ‘selected-row-changed’ and ‘row-activated’ are sent. If you click on a selected row the signal ‘row-activated’ is sent, but the selection isn’t changed.

With this properties actually you expect that a click on a row changes the selection to this row only and activates it. If you hold down the Ctrl key no row will be activated but, the selection of the row is enabled/disabled, depending on the current state.
Comment 1 mhabrnal 2015-06-26 07:04:54 UTC
Would be nice to be able deselect a selected row if the property ‘activate-on-single-click’ is TRUE and ‘selection-mode’ is GTK_SELECTION_MODE_MULTIPLE.

We use the GtkListBox in gnome-abrt and there is a problem when you select a wrong row in multiple selection mode. You cannot fix the wrong selected row but you have to start to select from the beginning.
Comment 2 Matthias Clasen 2018-02-10 05:08:36 UTC
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 3 Christian Stadelmann 2018-02-11 17:52:38 UTC
This issue is still true with Gtk+ 3.92.1 and can easily be reproduced using gtk4-demo's "List Box" when setting the properties of the GtkListBox (see above) through GtkInspector.
Comment 4 Bastien Nocera 2018-02-11 18:43:08 UTC
A modification of the test case to show this bug would be useful (so as to avoid going through GtkInspector to reproduce the bug).
Comment 5 Christian Stadelmann 2018-02-11 19:34:46 UTC
Created attachment 368234 [details]
A glade file demonstrating the bug

The attached glade file is enough for reproducing the bug. Just open it in glade and click on the "Preview" button in glade.
Comment 6 lovetox 2018-04-05 21:10:26 UTC
CTRL/SHIFT + Click does also nothing.

although because of the bug we can not evaluate if CTRL + Click does something.

But Shift + Click should select a range which it does not
Comment 7 GNOME Infrastructure Team 2018-05-02 16:34:58 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gtk/issues/552.