[Glade-devel] bugs in glade3

[pborelli katamail com (Paolo Borelli)]

On Tue, 2004-01-13 at 14:36, Sridhar R wrote:
> [sorry if i have already posted this]
>
> Here is the list of bugs that I saw in glade3.
>
> * b: setting "Type hint" property for created windows
> leads to assert failure:
> (glade-3:6854): Gtk-CRITICAL **: file gtkwindow.c:
> line 1905 (gtk_window_set_type_hint): assertion
> `!GTK_WIDGET_VISIBLE (window)' failed
> Trace/breakpoint trap

Yes I saw this too. IIRC the problem is that this property can only be
set when the window has not been shown yet.
To fix it you can try to override this property in widgets/gtkwindow.xml
(if it doesn't exist you can create it and add it to gtk-base.xml) with
either the ignore() function or with a proper function in glade-gtk.c
which works around the problem.

> * b: clicking on "messagedialog" in palette leads to
> assert failure:
> (glade-3:6858): Gtk-CRITICAL **: file gtkimage.c: line
> 1017 (gtk_image_get_pixbuf): assertion
> `image->storage_type == GTK_IMAGE_PIXBUF ||
> image->storage_type
> == GTK_IMAGE_EMPTY' failed
> Trace/breakpoint trap

This is because we don't have an icon for the message-dialog at the
moment... feel free to draw one if you have the necessary gimp-fu :)

> * b: Open glade3. Create a new window. Now the
> property window should show the properties of that
> window.  Now click _inside_ the newly created window. 
> Now the property window should be empty.  The new
> windows can be selected by clicking its entry
> ("window1") in glade3 main window.  Now the property
> page shows the
>  properties again.  Now again click inside the new
> window.  Then try selecting the new window by clicking
> on the new window's entry on glade3 main window.  Now
> the properties won't show up.  Now go to 'signals' tab
> in Properties window.  Click on the button labeled
> '...'. oops! seg fault in assert statemenet
> g_return_if_fail (editor->class->signals != NULL); in
> glade_signal_editor_dialog_cb at line no 190

this is a bug: a good candidate to start your hacking... warm up your
gdb and figure out why that pointer is NULL :)

> (currently patched to include assert statements)
> now error will be ..: (after aplying g-signal-editor
> the patch)
> Glade-ERROR **: file glade-signal-editor.c: line 191
> (glade_signal_editor_dialog_cb): assertion failed:
> (editor->class)
> aborting...
> Aborted

This is the simple consequence of the failed assert.


The nice thing about hacking on a developement module as glade-3, is
that it has a lots of bugs to keep you busy... who needs a PlayStation2!
;^)


ciao
        paolo