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 154921 - canceling the editing may start it again
canceling the editing may start it again
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkTreeView
unspecified
Other Linux
: Normal normal
: Small fix
Assigned To: gtktreeview-bugs
gtktreeview-bugs
Depends on:
Blocks:
 
 
Reported: 2004-10-08 17:05 UTC by Matthias Clasen
Modified: 2018-02-10 03:29 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Matthias Clasen 2004-10-08 17:05:21 UTC 
If I edit a cell, then stop the editing by clicking on a different cell in the
same row, what actually happens is:

1) tree view stops editing in gtk_tree_view_stop_editing()
2) tree view calls gtk_tree_view_column_process_action(), which 
  starts (!) the editing again, connecting the focus out event handler
  in gtkcellrenderertext again
3) the entry looses focus, so the focus out event handler gets triggered
 and stops editing again
Comment 1 Federico Mena Quintero 2004-11-20 01:49:08 UTC 
There's a hack around this in gtkfilechooser.c:renderer_editing_canceled_cb(). 
When this bug gets fixed, we should remember to remove that hack :)
Comment 2 Kristian Rietveld 2006-12-10 20:08:21 UTC 
With which cell/column configuration is this easy to see?  I can't see it in gtk-demo or testtreeedit and didn't see something special in the file chooser after commenting out the work around there either.

Maybe this has been silently fixed meanwhile?  Would be cool if somebody could verify this :)
Comment 3 Matthias Clasen 2018-02-10 03:29:35 UTC 
We're moving to gitlab! As part of this move, we are closing bugs that haven't seen activity in more than 5 years. If this issue is still imporant to you and
still relevant with GTK+ 3.22 or master, please consider creating a gitlab issue
for it.