#x27;t already aware.
-Elden Armbrust
___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
David Necas (Yeti) wrote:
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"
:
Use g_signal_connect, rather than gtk_signal_connect.
I may have found out how to specifically use gtk-wimp per application.
When I have I will update this thread with my findings.
Thanks guys.
-Elden Armbrust
David Necas (Yeti) wrote:
On Fri, Mar 24, 2006 at 09:11:26PM -0600, Nickolai Dobrynin
r in a bit to see if the same code
does the same thing there.
-Elden Armbrust
Elden Armbrust wrote:
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 (ev
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
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 knowledgab
mp on
a per application basis, rather than a system wide GTK implementation?
Oh yes, and this is my first mailing to the list. Howdy all :)
-Elden Armbrust
___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
http://mail.gnome.org/ma
