Re: Issue with gtk+ 2.8.15 for win32

2006-03-25 Thread David Necas (Yeti)
On Fri, Mar 24, 2006 at 09:11:26PM -0600, Nickolai Dobrynin wrote: 1. Use destroy rather than destroy_event as the second argument to your call. destroy is a signal rather than an event. That was confusing. destroy-event (note the use of underscores was deprecated) is a signal too.

Re: Issue with gtk+ 2.8.15 for win32

2006-03-25 Thread Elden Armbrust
The whole thing is quite confusing. The code in the tutorial on the gtk site uses destroy_event, but uses g_signal_connect. Glade, however, appears to be using gtk_signal_connect. This, I assume, is why the tutorial code worked while the glade code didn't. So for future reference: Use

Re: Issue with gtk+ 2.8.15 for win32

2006-03-25 Thread David Necas (Yeti)
On Sat, Mar 25, 2006 at 07:11:36AM -0500, Elden Armbrust wrote: The whole thing is quite confusing. The code in the tutorial on the gtk site uses destroy_event, I can see only three signal connections there: to delete_event, destroy, and clicked (of the button), no destroy_event. but uses

Issue with gtk+ 2.8.15 for win32

2006-03-24 Thread Elden Armbrust
I'm not sure if this is a bug, error on my part, or otherwise, so I figured it best to ask the list. When exiting out of a program written in C using GTK+ 2.8.15, the process does not end (ever) but the window does close. Another question: Is there anyone knowledgable in how to use gtk-wimp on

Re: Issue with gtk+ 2.8.15 for win32

2006-03-24 Thread Elden Armbrust
Elden Armbrust wrote: I'm not sure if this is a bug, error on my part, or otherwise, so I figured it best to ask the list. When exiting out of a program written in C using GTK+ 2.8.15, the process does not end (ever) but the window does close. Another question: Is there anyone knowledgable in

Re: Issue with gtk+ 2.8.15 for win32

2006-03-24 Thread David Necas (Yeti)
On Fri, Mar 24, 2006 at 04:04:53PM -0500, Elden Armbrust wrote: When exiting out of a program written in C using GTK+ 2.8.15, the process does not end (ever) but the window does close. That is correct. Gtk+ does not terminate applications just because some of their windows was closed. So the

Re: Issue with gtk+ 2.8.15 for win32

2006-03-24 Thread Elden Armbrust
David Necas (Yeti) wrote: On Fri, Mar 24, 2006 at 04:04:53PM -0500, Elden Armbrust wrote: When exiting out of a program written in C using GTK+ 2.8.15, the process does not end (ever) but the window does close. That is correct. Gtk+ does not terminate applications just because some

Re: Issue with gtk+ 2.8.15 for win32

2006-03-24 Thread Elden Armbrust
It appears I have spoken too soon. I have added the following code to my project, yet it still continues to leave a process running. Code - (in interface.c, for the construction of wndMain) gtk_signal_connect (GTK_OBJECT (wndMain), destroy_event, GTK_SIGNAL_FUNC

Re: Issue with gtk+ 2.8.15 for win32

2006-03-24 Thread Nickolai Dobrynin
1. Use destroy rather than destroy_event as the second argument to your call. destroy is a signal rather than an event. 2. IIRC, gtk_signal_connect has been deprecated in favor of g_signal_connect. Regards, Nickolai On 3/24/06, Elden Armbrust [EMAIL PROTECTED] wrote: It appears I