Re: clist performance.

["Joshua Horvath" <Josh_Horvath-AJH051 email mot com>]

I don't think you can do anything about this.  I just browsed through the
gtkclist code and the select_all function just goes down the list and emits a
"select-row" signal for each row.  The select_row function, in turn, performs
a g_list_nth() search through the row list to find the selected row, so it's
going to be slow for large numbers of rows.

You might gain a little performance by freezing the clist before doing the
select_all and thawing afterwards, but it's probably not going to help much if
you're trying to select 100,000 rows.


-Josh

Christian Kreibich wrote:
> 
> Hi,
> 
> when I have a large number of entries (> 10,000) in a clist widget and
> do a "select all", performance really goes down the drain, it takes
> literally minutes to complete for 1e5 entries. I'm using multiple
> selection mode, see attached demo program. Can I do anything to avoid
> the performance hit?
> 
> Best regards,
> -- Christian.
> ________________________________________________________________________
>                    International Computer Science Institute, ACIRI Group
>                                                mailto:kreibich aciri org
> 
> _______________________________________________
> gtk-list mailing list
> gtk-list gnome org
> http://mail.gnome.org/mailman/listinfo/gtk-list