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 552902 - editing is canceled when a cell editable loses focus
editing is canceled when a cell editable loses focus
Status: RESOLVED DUPLICATE of bug 315280
Product: gtk+
Classification: Platform
Component: Widget: GtkTreeView
2.12.x
Other All
: Normal minor
: ---
Assigned To: gtktreeview-bugs
gtktreeview-bugs
Depends on:
Blocks:
 
 
Reported: 2008-09-19 14:30 UTC by Toon Verstraelen
Modified: 2010-10-10 03:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Toon Verstraelen 2008-09-19 14:30:19 UTC
Problem in detail:

When editing a cell in a tree view, the editing is canceled when one clicks on a button outside the tree view, and the entered value is discarded. One has to click in the tree view or press enter in order to save the new value. These are very limited conditions that are not straightforward for the end user. 

Consider for example a tree view in a dialog box. When one is editing a cell and one has entered the desired value, it is very natural to click immediately on the OK button without first pressing enter or clicking somewhere else. The effect is that the new value is discarded and because the dialog disappears directly, the user does not notice that the new value is not saved. This causes a lot of confusion to end users. I have to explain them over and over again that they first have to press enter.

Proposed solution:

The function gtk_cell_renderer_text_focus_out_event in gtkcellrenderertext.c should be modified. Now it just cancels editing. It should save the value in the tree model. The escape button should become the only way to cancel editing.

Thanks

Other information:
Comment 1 Federico Mena Quintero 2010-10-10 03:03:55 UTC

*** This bug has been marked as a duplicate of bug 315280 ***