Angelo,
Thank you SOOOO much. You hit the solution dead on. After you showed me
what was correct, I dug around and found the following description from
Havoc at:
http://gnomewww.sunet.se/mailing-lists/archives/gtk-list/1999-May/0378.shtml
If also tried your suggestion to use connect and emit_stop_by_name, it also
works.
Thanks a bunch,
Andy L.
-- Excerpt from above web page included --
Only GtkWindow (and therefore dialogs) actually receives key press events
from Gdk/X as far as I can tell, because Gtk never moves the X input focus
away from them. GtkWindow then dispatches the key event to the widget in the
window that has the Gtk input focus (which is different from the X input
focus).
If the last handler for the focus widget key press returns TRUE, then no
more processing is done. To install the last handler you'll have to use
gtk_signal_connect_after(). If the last handler returns FALSE, then
GtkWindow sends the key event to any accel group, and if that also returns
FALSE there are some default keybindings (such as space and the arrow keys).
Further complicating matters, there is a default key press handler for
GtkWidget that invokes any "bindings" the widget has. This default handler
runs before any user-connected handlers if you use gtk_signal_connect(),
that's why you have to use connect_after() if you want to have the last
handler.
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
