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 701899 - [regression] TreeView forgets to ellipsize after first resize and looses header text
[regression] TreeView forgets to ellipsize after first resize and looses head...
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Widget: GtkTreeView
3.8.x
Other Linux
: Normal normal
: ---
Assigned To: gtktreeview-bugs
gtktreeview-bugs
Depends on:
Blocks:
 
 
Reported: 2013-06-09 14:17 UTC by Christoph Reiter (lazka)
Modified: 2014-06-01 18:07 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
first draw; then after first resize (51.94 KB, image/png)
2013-06-09 14:17 UTC, Christoph Reiter (lazka)
Details

Description Christoph Reiter (lazka) 2013-06-09 14:17:38 UTC
Created attachment 246352 [details]
first draw; then after first resize

This commit broke my treeview setup somehow..

Treeview, one FIXED column with a CellRendererPixbuf, a second one with a CellRendererText, GROW_ONLY and ellipsize.

My current workaround is to set the second column to fixed as well.. which works and the column expands to the whole length... no idea why..(??)

Also the header disappears at the same time (see attached screenshot)

Bisected to this:

6d53c2339f79baa0b295ecc614f41f9daab2e132 is the first bad commit
commit 6d53c2339f79baa0b295ecc614f41f9daab2e132
Author: John Lindgren <john.lindgren@aol.com>
Date:   Tue Dec 18 02:06:12 2012 -0500

    Use minimum/natural size semantics
    
    Rewrites gtk_tree_view_column_request_width() and
    gtk_tree_view_size_allocate_columns() to respect the minimum and natural
    sizes that are already being returned by
    gtk_cell_area_context_get_preferred_width().
    
    The convoluted logic explained (not!) by this comment has been removed:
    “Only update the expand value if the width of the widget has changed, or
    the number of expand columns has changed, or if there are no expand
    columns, or if we didn't have an size-allocation yet after the last
    validated node.”  This logic seems to have been a workaround for the
    “jumping” behavior fixed in 16195ad and is no longer necessary.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=691751
Comment 1 Christoph Reiter (lazka) 2014-06-01 18:07:17 UTC
The above commit got reverted as part of https://bugzilla.gnome.org/show_bug.cgi?id=731054