Re: Questions about event percolation
- From: otaylor redhat com
- To: Ramiro Estrugo <ramiro netscape com>
- Cc: gtk-list redhat com
- Subject: Re: Questions about event percolation
- Date: 14 Apr 1999 16:24:36 -0400
Ramiro Estrugo <ramiro@netscape.com> writes:
> 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 ?
Ah, I see. You are worried about the event propagation
that X does, not just GTK+'s event propagation.
Calling:p
gtk_widget_add_events(button,GDK_POINTER_MOTION_MASK);
so that the events you receive have the right window field
should be harmless. The extra messages won't confuse the button
widget.
> Does that generate the same amount of traffic as opposed to not
> selecting motion events ? More ?
It doesn't generate any more traffic - the X server will
send a single event in either case. There will be a few
more GTK+ signals being emitted (to be precise, two more),
but the effect should be completely unnoticeable.
Regards,
Owen
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]