Re: Can a treeview do this?

[Gus Koppel <gtk spamkiller bytechase cx>]

kadil wrote:

> I may not have explained myself very well in my question to the
> world.  To describe it in words, I want:
>
> (1) the first child to be in the column next to the parent.
> (2) subsequent children to be below the first child
> (3) parent "cells" are to vertically span the child rows
> (4) I need visible borders between the cells
> (5) Just to be difficult, I want to code in csharp (mono and friends)
> (6) Accommodate thousands of rows with responsive performance.
>
> >  ________________________________________________________
> > |  Function | Funct Failure    |  Failure Mode           |
> >  --------------------------------------------------------
> > |to be able |slow leak         | worn washer             |
> > |control the|                  |-------------------------|
> > |rate of fl-|                  | damaged seat            |
> > |uid passing|------------------|-------------------------|
> > |thru the   |unable to control | seized                  |
> > |device     |flow at all       |-------------------------|
> > |           |                  | frozen                  |
> > |--------------------------------------------------------|

I think your sketch is quite clear. Your demands 1 to 4 can be fulfilled
by using a GtkTable with GtkLabels inside GtkFrames in each cell, as I
described. I don't know about late developments in GTK+ bindings for C#
but I think there should be support for it. At least this is being
worked on, AFAIK. As I prefer easiness over difficulty and native
performance over losings related to emulation, I stick with C when
programming GTK+.

Only weak point in the GtkTable based concept may be your demand of much
content in the table. However, I'd say you should give it a try. I think
building such a structure of thousands of widgets is the main
performance bottleneck. Display and navigation within such a
GtkScrolledWindow isn't necessarily that slow since GTK+ 2.x should
contain some appropriate optimizations to handle this, I think.