Path: utzoo!utgpu!water!watmath!clyde!rutgers!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: <880106182829.8.RWS@KILLINGTON.LCS.MIT.EDU>
Date: 6 Jan 88 23:28:00 GMT
References: <2776980073-2810538@Sierra>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 26


    Date: Thu, 31 Dec 87  17:21:13 CST
    From: Kerry Kimbrough <Kimbrough%dsg.csc.ti.com@RELAY.CS.NET>

	   (event-window (GETF event-keys
			       (CASE event-key
				 ((:configure-request ...) :parent)
				 ((:circulate-notify  ...) :event-window)
				 (otherwise                :window)))))

    Servicable, but it would be cleaner and more reliable if it was always the same
    keyword (say, :event-window).  Same goes for event dispatching, too.

(I note that the C Xlib doesn't use uniform names, but uses a
by-position-in-structure kludge when matching windows.)

I would prefer not to make an incompatible change.  Better, it seems to
me, is to simply allow use of :event-window on all window-based events,
Thus, for example, :event-window could be used as a synonym for :parent
in :configure-request events.

The only "difficulty" is whether :event-window should be permitted in
queue-event and send-event.  It could either be disallowed, or require
that if both synonyms are given they must be equal, or say it "is an
error" if synonyms with differing values are given.  Off-hand, I would
lean to "is an error".