Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!ginosko!usc!apple!agate!shelby!decwrl!gilroy.pa.dec.com!klee
From: klee@gilroy.pa.dec.com (Ken Lee)
Newsgroups: comp.windows.x
Subject: Re: XSendEvent()
Message-ID: <1894@bacchus.dec.com>
Date: 5 Oct 89 16:54:55 GMT
References: <8910050100.AA21383@metropolis.super.org>
Sender: news@decwrl.dec.com
Reply-To: klee@decwrl.dec.com
Organization: DEC Western Software Laboratory
Lines: 15

In article <8910050100.AA21383@metropolis.super.org>, dsseewe@SUPER.ORG
(Daniel Seewer) writes:
> 		* This button merely sends Events to the scrollbar widget 
> 			Button press and Button release events.

While XSendEvent certainly could be used for communication within a
client, I think the overhead of doing this is much to high for most
applications.  XSendEvent is better used for communicating between
separate clients.  Examples are selection notification, window manager
synthetic events, and client message events.

Ken Lee
DEC Western Software Laboratory, Palo Alto, Calif.
Internet: klee@decwrl.dec.com
uucp: uunet!decwrl!klee