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 340200 - Editable shown in wrong position
Editable shown in wrong position
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Widget: GtkTreeView
2.8.x
Other Linux
: Normal normal
: ---
Assigned To: gtktreeview-bugs
gtktreeview-bugs
: 346822 (view as bug list)
Depends on:
Blocks: 345591
 
 
Reported: 2006-04-30 15:09 UTC by Torsten Schoenfeld
Modified: 2011-02-04 16:19 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Screenshot showing the incorrect positioning. (3.49 KB, image/png)
2006-04-30 15:09 UTC, Torsten Schoenfeld 		Details
Short Perl program demonstrating the problem. (691 bytes, text/plain)
2006-04-30 15:10 UTC, Torsten Schoenfeld 		Details

Description Torsten Schoenfeld 2006-04-30 15:09:29 UTC 
With HEAD of CVS, the entry widget of editable tree views is shown in the wrong position (too far to the right) in certain situations.  I can reproduce the problem reliably on nodes that have one or more ancestors, i.e. nodes which have one or more levels of indention.  The problem only occurs when you start the editing programmatically[1] or by using the keyboard; when you use the mouse, the editable is positioned correctly.

I attach a screenshot and a Perl program that demonstrates the problem.

[1] Via gtk_tree_view_set_cursor with TRUE for start_editing.
Comment 1 Torsten Schoenfeld 2006-04-30 15:09:59 UTC 
Created attachment 64567 [details]
Screenshot showing the incorrect positioning.
Comment 2 Torsten Schoenfeld 2006-04-30 15:10:38 UTC 
Created attachment 64568 [details]
Short Perl program demonstrating the problem.
Comment 3 Kristian Rietveld 2006-04-30 15:49:51 UTC 
Oh, good catch.  Prolly caused by the recent commit of the level indentation property.

Fixed on HEAD.
Comment 4 Torsten Schoenfeld 2006-06-17 17:51:19 UTC 
It looks like the same problem is also present in 2.8.18.
Comment 5 Kristian Rietveld 2006-06-26 16:28:04 UTC 
I am not sure if there's going to be another 2.8.x release ... (unfortunately I don't have the time to maintain 2.8.x next to HEAD).
Comment 6 Matthias Clasen 2006-06-27 07:32:07 UTC 
I'll do a 2.8 release soon.
Comment 7 palfrey 2006-10-17 10:58:26 UTC 
I can't reproduce this with GTK 2.10.6 (specifically debian's 2.10.6-2 package), and so this should probably be closed.
Comment 8 Murray Cumming 2006-10-17 11:14:31 UTC 
We still need that 2.8 release to fix distributions that can't upgrade to 2.10, such as Ubuntu Dapper.
Comment 9 Kristian Rietveld 2006-10-27 20:14:21 UTC 
*** Bug 346822 has been marked as a duplicate of this bug. ***
Comment 10 Kristian Rietveld 2007-08-21 11:59:28 UTC 
I don't think another 2.8.x is going to happen -- closing.