Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!lll-tis!ames!ucbcad!ucbvax!ZERMATT.LCS.MIT.EDU!RWS
From: RWS@ZERMATT.LCS.MIT.EDU (Robert Scheifler)
Newsgroups: comp.windows.x
Subject: Re: CLX question
Message-ID: <871231132319.1.RWS@KILLINGTON.LCS.MIT.EDU>
Date: 31 Dec 87 18:23:00 GMT
References: <2776955443-1354824@Sierra>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 18


    Date: Thu, 31 Dec 87  10:30:43 CST
    From: Kerry Kimbrough <Kimbrough%dsg.csc.ti.com@RELAY.CS.NET>

	   Implementing the effect of XWindowEvent/XCheckWindowEvent in CLX is
    certainly doable, but it is ponderous. This is because the event keyword used to
    name the event's "addressee" is different for different event types. This is a
    nit that would be worth cleaning up, preferably by using the same keyword for
    the addressee everywhere; this solution would also enable a cleaner
    implementation of event dispatching in object-oriented systems like CLUE.

Could you explain this, perhaps with an example?  Can you list where
keyword use isn't uniform?  The event names are NOT the same as the mask
names; this is true in both Xlib and CLX.  Xlib internally has a table
mapping event name to mask bit that gets used in XWindowEvent.  A
function mapping from event-name key to event-mask key (and perhaps one
from event-mask key to list of event-name key) can certainly be defined
and would be reasonable to make part of the CLX interface, if someone
wants to supply the code.