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 162957 - Discrete scrolling in GtkTreeView
Discrete scrolling in GtkTreeView
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkTreeView
unspecified
Other All
: Normal enhancement
: Small feature
Assigned To: gtktreeview-bugs
gtktreeview-bugs
scrolling
Depends on:
Blocks:
 
 
Reported: 2005-01-04 21:47 UTC by Billy Biggs
Modified: 2018-04-15 00:27 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Billy Biggs 2005-01-04 21:47:10 UTC 
It would be useful to support a scrolling mode where the top of the GtkTreeView
widget is always aligned to an item.  Currently, GtkTreeView scrolls completely
based on pixels, making it more difficult to scan large lists quickly in a small
amount of vertical space, especially when scrolling by pages.  As well, some
applications expect this behaviour and change state based on the topmost visible
item in the list.  For example:

  https://bugs.eclipse.org/bugs/show_bug.cgi?id=74739
Comment 1 Kristian Rietveld 2006-07-01 19:10:15 UTC 
I really doubt whether this is possible without changes to GtkAdjustment ...
Comment 2 Hans van Hintum 2010-02-03 21:07:32 UTC 
I have added a patch that performs this discrete scrolling for the treeview. This patch is not changing the GtkAdjustment implementation, but only changes the gtktreeview code.

I have implemented this patch on top of a patch to implement a pixmap as background for the treeview (71926), but the code is clearly identified by the comments "bug 162957" and "bug 162957 - end"
Comment 3 Matthias Clasen 2018-02-10 05:06:33 UTC 
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 4 Matthias Clasen 2018-04-15 00:27:17 UTC 
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla.

If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:

https://gitlab.gnome.org/GNOME/gtk/issues/new