The glade file is set to "Object names are unique within toplevels" which fits the way my glade file is set up. Maybe I should get a fresh copy of glade-3. I'm at Glade 3.6.3 On Mon, Jul 27, 2009 at 12:49 PM, Tristan Van Berkom<tvb@xxxxxxxxx> wrote: > Oops I seemed to have replied to the middle of this thread. > > If its an issue with the widget id uniqueness, then you can > go in Glade's project preferences and toggle the naming policy > setting (and please use a recent build of Glade to make sure > the policy works correctly, it had some bugs earlier this year). > > Cheers, > -Tristan > > On Mon, Jul 27, 2009 at 12:44 PM, Tristan Van Berkom<tvb@xxxxxxxxx> wrote: >> On Fri, Jun 26, 2009 at 9:11 AM, Gerald Britton<gerald.britton@xxxxxxxxx> wrote: >> [...] >>> 1. when and why is the method gtk_button_box_set_child_secondary >>> called by the add_from_file method? >> >> The fastest and easiest way to find out whats going on is to follow >> Paul's advice and simply run it once in gdb with a breakpoint on g_log. >> >> Thats what I would do to pinpoint exactly whats going on. >> (it could be a malformed Glade file and maybe a bug in Glade, >> it could also mean a bug in GTK+ parsing GtkButtonBox's). >> >>> 3. Can the text of the error message be changed to include the name of >>> the widget that has the problem, if available? >> >> Yes, you should ask the GTK+ team to do that by filing a bug against >> gtk+:GtkBuilder, those messages can trigger without GtkBuilder parsing >> the UI but in that case gtk_buildable_get_name() will still return the >> widget's class name by default. >> >> Cheers, >> -Tristan >> > -- Gerald Britton _______________________________________________ gtk-list mailing list gtk-list@xxxxxxxxx http://mail.gnome.org/mailman/listinfo/gtk-list
