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 318406 - TreeView search should look in collapsed branches
TreeView search should look in collapsed branches
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkTreeView
unspecified
Other All
: Normal enhancement
: Medium feature
Assigned To: gtktreeview-bugs
gtktreeview-bugs
Depends on:
Blocks:
 
 
Reported: 2005-10-10 01:08 UTC by Tim Mitchell
Modified: 2018-04-15 00:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8



Description Tim Mitchell 2005-10-10 01:08:29 UTC
I have just discovered this feature and added it to our app which can have a
rather large project tree structure. With larger trees users tend to have alot
of branches collapsed for ease of navigation, but when searching for something
want to search the entire tree.

Currently the typeahead/search only checks visible rows, it would be helpful
(for my app) to be able to search hidden nodes as well (expanding the tree as
required to display them when found).

A GtkTreeView.search_hidden property would be how I would implement it.
Comment 1 Matthias Clasen 2015-02-16 14:16:08 UTC
I've prototyped this in GtkInspector recently.
Comment 2 Matthias Clasen 2018-02-10 05:24:53 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 3 Matthias Clasen 2018-04-15 00:33:01 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