On Mon, Sep 22, 2008 at 6:46 PM, Matthias Clasen <[EMAIL PROTECTED]> wrote: > On Mon, Sep 22, 2008 at 12:41 PM, Patryk Zawadzki <[EMAIL PROTECTED]> wrote: >> That's what I proposed. If it's != 0, force it to 0 and issue a >> warning. Spin controls have no concept of data set so there is no such >> thing as a page and therefore there's no use for limiting the offset >> to a certain subrange of (min, max). It's a two-three line change for >> GTK and was already worked around in libglade (patch posted earlier in >> this thread). > That seems like a reasonable proposal, assuming that most of the > breakage is in spin buttons.
>From what I've learned from glade3, it only sets the values for GtkAspectFrame and GtkSpinButton. The only affected widget seems to GtkSpinButton (that's why I decided to leave aspect frame out of my patch posted earlier). Are there any examples of broken aspect frame behavior? Are there more widgets that got the adjustments from glade2? I didn't have the time to review glade2 code yet. In any case, gtk+ seems right the correct place to ignore the values as there were reports of broken examples that created widgets directly (thus libglade workarounds provide limited coverage). -- Patryk Zawadzki _______________________________________________ desktop-devel-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/desktop-devel-list
