RE: connecting a callback to a "key_press_event" signal on a button

["Erik Simonsen" <erik pinksheets com>]

I corrected that, but regardless, gtk_signal_* functions are supposed to
proxy the glib functions.  I figured out that the problem had to do with
signal propogation.  Some of my callbacks were void functions when they need
to be returning false in order to allow the signal to propogate.  The
strange thing was that those callbacks were attached to the top level
window.  I thought that if a button had focus and a key_press_event
happened, its callback should be called before the signal was propogated to
the parent and then the parent's window.  I don't understand why a parent's
signal should affect the child.

-----Original Message-----
From: gtk-app-devel-list-admin gnome org
[mailto:gtk-app-devel-list-admin gnome org]On Behalf Of Alberto Cabello
Sánchez
Sent: Friday, August 30, 2002 2:16 AM
To: gtk-app-devel-list gnome org
Subject: RE: connecting a callback to a "key_press_event" signal on a
button


I thought it was (in GTK 2) g_signal_connect, not gtk_signal_connect...
--
---------------------------------------------------
Alberto Cabello Sánchez <alberto cabello hispalinux es>
Debian GNU/Linux 2.4.19
---------------------------------------------------
_______________________________________________
gtk-app-devel-list mailing list
gtk-app-devel-list gnome org
http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list