I think I might just have to go with your idea and store the entire array of current values before I check for user-changes. Like I said, this isn't a small chunk, but so what. It sucks, it's a kluge, but allowing the hscale to move forward the then forcing it back will (or should) work, and that's more promise than I've seen in the last three days working on this.
So, although I still believe there's a better way to do this, I have to say thanks for getting me to look at this from a different perspective. Perhaps I'll figure out the correct way someday -- just not this day. > -----Original Message----- > From: gtk-app-devel-list-boun...@gnome.org > [mailto:gtk-app-devel-list-boun...@gnome.org] On Behalf Of > Michael Torrie > Sent: Monday, August 10, 2009 2:44 PM > To: Gtk app list > Subject: Re: Can't quite get my head around this, can anyone help? > _______________________________________________ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
