From c042ad3bf54babfb80f0e1f15e69401b9447e34e Mon Sep 17 00:00:00 2001 From: compudj Date: Tue, 25 May 2004 00:15:12 +0000 Subject: [PATCH] minor add git-svn-id: http://ltt.polymtl.ca/svn@540 04897980-b3bd-0310-b5e0-8ef037075253 --- .../lttv/modules/gui/lttvwindow/lttvwindow/viewer.h | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/ltt/branches/poly/lttv/modules/gui/lttvwindow/lttvwindow/viewer.h b/ltt/branches/poly/lttv/modules/gui/lttvwindow/lttvwindow/viewer.h index d332da57..f3aceb59 100644 --- a/ltt/branches/poly/lttv/modules/gui/lttvwindow/lttvwindow/viewer.h +++ b/ltt/branches/poly/lttv/modules/gui/lttvwindow/lttvwindow/viewer.h @@ -132,8 +132,16 @@ instead of just one. That means that X events are delivered by the glib main loop directly to the widget corresponding to the GdkWindow affected by the X event. -Event delivery to a widget emits a signal on this widget. Signal emission and -propagation is described there : +Event delivery to a widget emits a signal on that widget. Then, if a handler +is connected to this widget's signal, it will be executed. There are default +handlers for signals, connected at class instantiation time. There is also +the possibility to connect other handlers to these signals, which is what +should be done in most cases when a viewer needs to interact with X in any +way. + + + +Signal emission and propagation is described there : http://www.gtk.org/tutorial/sec-signalemissionandpropagation.html -- 2.34.1