Comments on: Three million rows in a GtkTreeView http://pvanhoof.be/blog/index.php/2006/01/13/three-million-rows-in-a-gtktreeview From the mind of Philip Sat, 13 Mar 2010 16:06:15 +0000 http://wordpress.org/?v=2.0.2 by: doverman http://pvanhoof.be/blog/index.php/2006/01/13/three-million-rows-in-a-gtktreeview#comment-37953 Sat, 18 Jul 2009 15:58:06 +0000 http://pvanhoof.be/blog/index.php/2006/01/13/three-million-rows-in-a-gtktreeview#comment-37953 How can I get the sample code?? https://svn.cronos.be/svn/custom-treemodel-demo/trunk ask me for a user and pwd How can I get the sample code??
https://svn.cronos.be/svn/custom-treemodel-demo/trunk ask me for a user and pwd

]]> by: Murray Cumming http://pvanhoof.be/blog/index.php/2006/01/13/three-million-rows-in-a-gtktreeview#comment-26298 Tue, 01 Apr 2008 14:45:47 +0000 http://pvanhoof.be/blog/index.php/2006/01/13/three-million-rows-in-a-gtktreeview#comment-26298 But how can you avoid having gtk_tree_model_iter_next() called three million times in gtk_tree_view_build_tree()? But how can you avoid having gtk_tree_model_iter_next() called three million times in gtk_tree_view_build_tree()?

]]> by: pvanhoof http://pvanhoof.be/blog/index.php/2006/01/13/three-million-rows-in-a-gtktreeview#comment-553 Wed, 19 Apr 2006 17:33:14 +0000 http://pvanhoof.be/blog/index.php/2006/01/13/three-million-rows-in-a-gtktreeview#comment-553 Interesting, I'll take a look Interesting, I’ll take a look

]]> by: hoa http://pvanhoof.be/blog/index.php/2006/01/13/three-million-rows-in-a-gtktreeview#comment-552 Wed, 19 Apr 2006 13:45:06 +0000 http://pvanhoof.be/blog/index.php/2006/01/13/three-million-rows-in-a-gtktreeview#comment-552 for etPanX, I am using a customized tree model : http://dinh.dyndns.org/~dinh/blog/etpanX-2006-01-02-bis.tar.gz http://dinh.dyndns.org/~dinh/blog/etpan-gtk-tree-model-types.h http://dinh.dyndns.org/~dinh/blog/etpan-gtk-tree-model.c http://dinh.dyndns.org/~dinh/blog/etpan-gtk-tree-model.h Since GtkTreeView work with GtkTreePath, GtkTreeView is slow. for every node, we have to know its index. Which can lead to two solutions : either : - determining the path of the element, which can be slow. - or caching the index for each node, which will lead to a performance problem when an element will be inserted, you'll have to update every indexes. You used the first solution. I used the second solution. My model is additionally a tree. The slowness will show when adding or removing elements. for etPanX, I am using a customized tree model :
http://dinh.dyndns.org/~dinh/blog/etpanX-2006-01-02-bis.tar.gz

http://dinh.dyndns.org/~dinh/blog/etpan-gtk-tree-model-types.h
http://dinh.dyndns.org/~dinh/blog/etpan-gtk-tree-model.c
http://dinh.dyndns.org/~dinh/blog/etpan-gtk-tree-model.h

Since GtkTreeView work with GtkTreePath, GtkTreeView is slow.
for every node, we have to know its index. Which can lead to two solutions : either :
- determining the path of the element, which can be slow.
- or caching the index for each node, which will lead to a performance problem when an element will be inserted, you’ll have to update every indexes.

You used the first solution.
I used the second solution.

My model is additionally a tree.
The slowness will show when adding or removing elements.

]]>