Thanks again jeff,
> Just a guess: but the signature of your callback is
> not
> correct for a delete event.
> One example that I know works for me, and I use this
> in many places:
>
> gboolean
> on_ancillary_window_delete_event (GtkWidget
> *widget,
> GdkEvent
> *event,
> gpointer
> user_data)
> {
> gtk_widget_hide(widget);
> g_print ("ancillary window delete event\n");
>
> /* some non-GTK utility code snipped here */
>
>
> return TRUE; /* stop the signal from propagating, if
> it
> propagates then it will eventually lead to
> a destroy event ... we will only hide the windows
> */
> }
>
> Also, I would disconnect the destroy and destroy_event
>
> or hook destroy_event up to a function that only tells
> you it was invoked (for debugging).
>
> One other thing, is the window you are working with
> really a pop-up or is a regular GtkWindow or a
> GnomeApp. GtkPopup's are a slightly different animal.
Unfortunately, changing the signature and dispatching the destroy and
delete events to several callbacks does not solve the problem (same
error).
However, i am wondering about the changes in libglade behavior when i
choose
one of "Top Level,Popup,dialog" options as type for the window.
Apparently, i see no difference in my case.
I definitively lack a documentation about these subtile options.
My application is a gnome one, so maybe i'd better use GNOME build-in
functions
for a preference window (they maybe already handle such destroy events).
However, i'd prefer use libglade as much as possible and it is not
very statisfactory not to know if glade can handle this correctly as the
interface suggests.
S.G.
+---------------------------------------------------------------------+
To unsubscribe from this list, send a message to [EMAIL PROTECTED]
with the line "unsubscribe glade-devel" in the body of the message.
