GNOME Bugzilla – Bug 678570
Setting GTKTreeViewColumn "sizing" to GTK_TREE_VIEW_COLUMN_AUTOSIZE causes bogus toggle signal
Last modified: 2018-04-15 00:26:09 UTC
Created attachment 216957 [details] Example program to reproduce the issue Hi all, I found this bug whilst working on a GUI application on Debian Squeeze. The bug manifests itself when editing a text field in a row containing at least one text column and a toggle button. What happens is that when setting the GtkTreeViewColumn "sizing" attribute to GTK_TREE_VIEW_COLUMN_AUTOSIZE, editing one of the text fields causes a bogus "toggle" signal to be sent to a toggle button on the same row. This caused us an issue as we used the toggle button as a quick way of deleting a row within our application, and so as people were editing text fields, the row would completely disappear. In order to reproduce: - Compile the attached mcatest.c file and run it - Verify that clicking on the toggle button causes a message to appear on stderr - Click on the text "Column3" in the row under "Textcol3" as if you were about to edit the row - Now click directly on the text "Column1" under "Textcol1" - Verify that the toggle message unexpectedly appears on stderr It is possible to see that it is the "sizing" attribute that causes this by simply swapping around the lines beginning "g_object_set(colX_column..." with their commented version for each column and recompiling. Now repeating the test shows that the bogus "toggle" signal is no longer sent, which is the expected behaviour. ATB, Mark.
GTK 2.20 is not supported anymore. Please try with 3.4, 3.2 (or 2.24.10 if there really is no chance to use recent GTK versions) and report back if this is still an issue.
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.
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla. If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab: https://gitlab.gnome.org/GNOME/gtk/issues/new