Re: Questions about event percolation

[Ramiro Estrugo <ramiro netscape com>]

otaylor@redhat.com wrote:
> 
> No way to tell GTK+ not to emit the signals, but it should
> be easy enough to filter them out in your handler:
> 
>  if (event->window != GTK_LAYOUT (layout)->bin-window)
>     return TRUE;

Yes, all this does is save a signal.  See below...

> 
> > If not, are there any effeciency concerns about having to install every
> > single signal on every signal child (along with setting the events,
> > which i preseme ultimately does the x lib selection of event) ?
> 
> Well, it will be slower and more space intensive. The speed
> probably isn't a huge concern, but memory bloat may be significant.
> 
> It is 32 bytes per signal handler, and there are 9 signals
> that are propagated in this way, so that is 288 bytes per
> widget.
> 
> Regards,
>                                         Owen

Im not concerned about memory consumption or signal processing overhead.

What im concerned about is excessive traffic between the client and the
server.

What exactly are the side effects of:

gtk_widget_add_events(button,GDK_POINTER_MOTION_MASK);

where button is a child of the container in question ?

Does that generate the same amount of traffic as opposed to not
selecting motion events ?  More ?

thanks for repyling

-re