Ronald Bultje <[EMAIL PROTECTED]> writes:
> I cam as far as to see that the delete/destroy signals don't reach their
> respective functions at all.
> If it gets delete/destroy, it will unrealize the widget, then destroy the
> widget (these commands finish), but then, it doesn't reach the
> destroy/delete signal handlers in my app. So it doesn't gtk_main_quit();
>
> So something goes wrong between widget-unrealize/-destroy and
> app-delete/-destroy.
>
To wildly speculate, keep in mind that the "destroy" signal default
handler disconnects all signal handlers.
i.e. if you gtk_signal_connect() to destroy it will be called, but if
you gtk_signal_connect_after() it will not, and no connections to
other signals will work after "destroy" has been emitted.
But the code you posted looks like it should work (the delete_event
handler wasn't needed, since it returned FALSE it just allowed the
default action of destroying the window to happen; the destroy handler
should have been called on delete_event for that reason).
Havoc
_______________________________________________
gtk-list mailing list
[EMAIL PROTECTED]
http://mail.gnome.org/mailman/listinfo/gtk-list
