Re: GtkRange rewrite

Havoc Pennington <hp redhat com> writes:

> OK, all issues I know of are now fixed, and except where noted in
> ChangeLog, this range is indistinguishable from old GtkRange. testgtk
> range controls test is pixel-for-pixel identical as far as I
> see. Update policies work (unless I misunderstand them) and the
> sprintf/scanf digit-rounding hack is back in action.

Do we really need update policies?  I think Java's way of telling you
whether the adjustment/model/whatever is continously changing is
better because you leave the actual update policy up to the user of
the widget.  That's why I wrote the GtkHSV thingy that way :)


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]