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 596514 - "row-activated" signal not emitted properly after double-clicking on editable part of GtkCellRendererText in GtkTreeViewColumn.
"row-activated" signal not emitted properly after double-clicking on editable...
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkTreeView
2.16.x
Other Windows
: Normal normal
: ---
Assigned To: gtktreeview-bugs
gtktreeview-bugs
Depends on:
Blocks:
 
 
Reported: 2009-09-27 16:17 UTC by Patrick
Modified: 2018-04-14 23:54 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Patrick 2009-09-27 16:17:10 UTC
If you:

1) Create a GtkTreeView...

2) Use a GtkListStore as the model...

3) Pack a GtkCellRendererPixbuf and GtkCellRendererText next to each other into a single GtkTreeViewColumn...

4) Make the text column editable...

5) Double-click the text in a row that hasn't already been selected (if it was already selected, double-clicking it would allow you to edit the text)...

... then the "row-activated" signal will not be emitted properly.

However, if you double-click the pixbuf instead of the text, then the "row-activated" signal will be emitted properly.
Comment 1 Christian Boxdörfer 2015-12-14 11:24:27 UTC
Since this bug is still valid, is there any chance of this getting fixed, or is this intended behavior?
Comment 2 Matthias Clasen 2018-02-10 04:53:59 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 Matthias Clasen 2018-04-14 23:54:50 UTC
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