Open GoogleCodeExporter opened 9 years ago
Note this problem happens in Windows or X11 versions. Horizontal scroll is no
more...?
Original comment by reardo...@gmail.com
on 29 Jan 2014 at 10:12
It's in a ScrolledWindow with the horizontal policy set to automatic, it's
always been that way.
Not sure why automatic doesn't seem anymore, so I've tried setting it to
always. Does it work for you?
Original comment by a...@eth0.org.uk
on 29 Jan 2014 at 10:34
Nope, that just added a scrollbar that doesn't scroll.
So I've disabled restoring column sizes from config as a workaround, since it
sucks less than not being able to scroll. The columns were set to fixed widths
on load, and GTK doesn't seem to add these up to determine the size of the
treeview. It used to work...
Original comment by a...@eth0.org.uk
on 29 Jan 2014 at 11:21
I do use my own column sizes and order. But I might be the only one.
Original comment by weba...@gmail.com
on 30 Jan 2014 at 5:20
I use it too and would like to put it back, this is a workaround in the
meantime.
Original comment by a...@eth0.org.uk
on 30 Jan 2014 at 10:14
Thanks! Seems to be back in working order now. Great work!
Original comment by weba...@gmail.com
on 15 Feb 2014 at 8:57
Same problem on Ubuntu Linux 13.10 64 bits.
git revision 3343101d993e
I don't see the horizontal scroll in classic view.
Original comment by decedion
on 6 May 2014 at 12:48
This is definitely a bug in GTK which I have reported. Can't find any good
workaround, so autosize columns is the best workaround available.
https://bugzilla.gnome.org/show_bug.cgi?id=731054
Original comment by a...@eth0.org.uk
on 31 May 2014 at 7:02
I don't understand the cdd62e21a859 revision (making the columns fixed again).
this yeilds worse behavior. Maybe we are running into different issues with
our builds. Why is the revision better? In my build, revision cdd62e21a859
gives me expando-columns that are unusable, basically I cannot control the
width at all because of auto-expansion (and the poor algorithm used by gtk3 to
expand).
Original comment by reardo...@gmail.com
on 20 Jun 2014 at 3:24
Original issue reported on code.google.com by
weba...@gmail.com
on 7 Oct 2013 at 7:15