Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!ames!ucbcad!ucbvax!hplabs!hp-pcd!hpcvlo!bobmi
From: bobmi@hpcvlo.HP.COM (Bob Miller)
Newsgroups: comp.windows.x
Subject: Re: X toolkit
Message-ID: <3940039@hpcvlo.HP.COM>
Date: Mon, 26-Oct-87 12:59:01 EST
Article-I.D.: hpcvlo.3940039
Posted: Mon Oct 26 12:59:01 1987
Date-Received: Fri, 30-Oct-87 02:11:23 EST
References: <919.8710211845@latlog.co.uk>
Organization: Hewlett-Packard Co., Corvallis, OR, USA
Lines: 16



In the new X Toolkit widgets are the coin of the realm.  And every widget
contains a window.  XtAddEventHandler (aside from doing an XSelectInput on
the specified event and window) attaches the event handler to the core part
of the widget instance structure.  When the event of interest finally occurs 
it is from this widget event table that the handler procedure is taken.
So, in order to use XtAddEventHandler you will need to surround your
window with a widget structure.

As you suspected, the dispatcher has no facilities for notifying your
program that an event did not belong to any widget.  Short of rewriting
XtDispatchEvent (one of the 2 routines in XtMainLoop) you will have to live 
with this. 

--Bob Miller