Comments on: treeview tips

By: Stefan Kost

Stefan Kost — Thu, 16 Jul 2009 10:58:57 +0000

Isn’t gtk_cell_renderer_set_fixed_size(renderer, 1, -1); setting the width to “1″?

By: otte

otte — Sun, 12 Jul 2009 11:30:45 +0000

While there might be some optimizations that can be done to rduce the pain, when people do bad things, in general these problems cannot be “fixed”. All of the things I mentioned are things that are at least O(n), so need to be done at least once per row. And the more rows you add, the more time it takes.

So in the end this blog post is just a call to people to be aware that a lot of stuff they do in tree views is stuff that’s in an inner loop. And inner loops just have to be fast.

By: Richard

Richard — Sat, 11 Jul 2009 00:45:56 +0000

Is it possible to “fix” GtkTreeView to avoid these issues?

By: Rui

Rui — Fri, 10 Jul 2009 21:28:19 +0000

Ei, nice tips! Maybe some of this text should go into the gtk+ docs?

By: otte

otte — Fri, 10 Jul 2009 21:07:11 +0000

Benoît, that is one of the cases where it probably is useful. In fact, this is what the _set_attributes() function does when you set a number column as the text property of a text cell renderer.
You just have to be aware of the issues I pointed out above.

By: Benoît

Benoît — Fri, 10 Jul 2009 20:54:10 +0000

I’m quite disappointed about gtk_tree_view_column_set_cell_data_func . A while ago, i moved a lot of code to it, thinking it was the best way to format numbers. Now you tell me it’s quite slow …

By: Andreas Tunek

Andreas Tunek — Fri, 10 Jul 2009 20:09:43 +0000

You rock! Please keep up the good work!

By: lariq

lariq — Fri, 10 Jul 2009 19:38:16 +0000

GtkTreeView can give you a hard time. Especially if you do things like using a custom model forwarded to a GtkTreeViewFilter with a custom view and then you want to do drag’n'drop from different sources. Fun