Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!pasteur!dent.Berkeley.EDU!davidh
From: davidh@dent.Berkeley.EDU (David S. Harrison)
Newsgroups: comp.windows.x
Subject: XtDispatchEvent under X11R3
Keywords: X Toolkit, Event Handling
Message-ID: <9536@pasteur.Berkeley.EDU>
Date: 5 Feb 89 23:51:43 GMT
Sender: news@pasteur.Berkeley.EDU
Reply-To: davidh@ic.Berkeley.EDU
Followup-To: comp.windows.x
Organization: UC Berkeley Electronics Research Lab
Lines: 21

In the manual "X Toolkit Intrinsics - C Language Interface" for
XV11R3,  XtDispatchEvent is declared as a boolean function that
returns _True_ if the event was dispatched to a handler and
_False_ if no appropriate handler was found (pg. 70).  The header
file <X11/Intrinsic.h> declares the function as void.  The 
implementation (in Event.c) also declares the function as void.  
I assume this is a documentation bug.

More importantly,  is this concept gone forever?  I have an
application I am migrating to the toolkit.  For the
interim,  I have both widgets and windows.  I would like
to write my own event loop where I can pass events
to XtDispatchEvent first and if the event is not a
toolkit event,  handle it myself.  I suppose I can determine
whether I can handle the event before passing it to
the toolkit but it would be more convenient the other
way around.  Opinions?

			David Harrison
			UC Berkeley Electronics Research Lab
			(davidh@ic.Berkeley.EDU, ...!ucbvax!ucbcad!davidh)