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 85778 - search in unexpanded trees
search in unexpanded trees
Status: RESOLVED WONTFIX
Product: gtk+
Classification: Platform
Component: Widget: GtkTreeView
2.0.x
Other Linux
: Normal enhancement
: ---
Assigned To: gtktreeview-bugs
gtktreeview-bugs
Depends on:
Blocks:
 
 
Reported: 2002-06-18 15:16 UTC by Fernando Herrera
Modified: 2011-02-04 16:11 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Fernando Herrera 2002-06-18 15:16:03 UTC
Current built-in search is not very usefull in most applications. It's
because it only searchs in the visible tree, and not in the unexpanded
items. For most applications user wants to search in the full tree (for
example, gconf-editor or mime-type capplets)
Comment 1 Kristian Rietveld 2002-10-05 11:56:20 UTC
The idea you are proposing, is a nice one. However we don't think we
should implement this in the treeview, because this will cause lots of
unwanted behaviour. For example, a filesystem model only reads the
next directory if the node for that directory is being expanded. So if
you're going to search through all unexpanded trees, it may start
reading every directory on your hard disk, on big volumes this will
take ages. Other than that it will use a lot of memory.

So this is not something we want to happen. The same reason is valid
for the gconf-editor tree (reading the complete gconf-editor tree
isn't really fast either), and most other models where this feature
could be useful. Not all of them though.

In summary, I think it's a nice idea, but it's not a good idea to
implement it as it will probably cause a lot of problems.