Sorry for the false alarm, I have figured what was wrong. It turned out that CanvasGroup was not the child of the canvas. Instead, they were both children of the canvas's parent. So connecting the overall handler to the parent's signal (insead of canvas's signal) solved the problem.
I guess it's obvious when one reads the help, so I apologize for a silly question. Alex On Mon, 2004-06-21 at 13:17, Alex Roitman wrote: > I'm trying to figure out the proper signal handling for the following > situation. I have gnome.canvas object, with some > gnome.canvas.CanvasGroup things added to it. I would like to have two > handlers for the events: one when e.g. the click is made over > CanvasGroup and another one when e.g. click is made elsewhere in the > parent canvas. > > If I just define two handlers then, when I right-click over the > CanvasGroup I get two handlers kick in one after another. > > I read FAQ and tried stopping the signal emission after the first > handler is done, to no avail. The thing seems to be that stop_emission() > and emit_stop_by_name() only apply to the same object (CanvasGroup). > > How do I prevent parent canvas from handling a signal already handled by > the CanvasGroup? Should I just watch the coordinates of the event, or is > there a way to communicate between the two objects? -- Alexander Roitman http://ebner.neuroscience.umn.edu/people/alex.html Dept. of Neuroscience, Lions Research Building 2001 6th Street SE, Minneapolis, MN 55455 Tel (612) 625-7566 FAX (612) 626-9201
signature.asc
Description: This is a digitally signed message part
_______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
