Re: Proposed GtkTreeView API change
- From: vishnu pobox com
- To: Jonathan Blandford <jrb redhat com>
- Cc: gtk-devel-list gnome org
- Subject: Re: Proposed GtkTreeView API change
- Date: Mon, 10 Sep 2001 12:10:15 -0700
On Mon, Sep 10, 2001 at 02:49:54PM -0400, Jonathan Blandford wrote:
> Currently GtkTreeView has a "range_changed" signal on it that is
> supposed to let the view know when a series of rows change. It was
> added when signals were slower, and sizing of rows was different.
> Unfortunately, since then row sizing has changed such that you need to
> walk the range anyway, and you emit a bunch of signals per row (a
> "property_notify" per column). Additionally, none of the models emit
> it, and the TreeView doesn't support it. Changing GtkTreeModelSort to
> support it will be a nightmare. All this leads me to believe that we
> need to change it to be just "changed" (or maybe "row_changed").
"row-changed" sounds good.
> I'd like to do this, though it will break anyone's code who's using
> this or writing their own model. Comments??
i wrote my own model, but i didn't implement "range-changed" yet.
While your at it, consider renaming "reordered" since i mistakenly
thought that the "reordered" signal was for reordering a single
row, instead of all the rows. Perhaps "rows-reordered" or
"rows-resorted" or "rows-permuted" would be good.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]