Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!ora!bloom-beacon!dont-send-mail-to-path-lines
From: rws@expo.lcs.mit.EDU (Bob Scheifler)
Newsgroups: comp.windows.x
Subject: re: Xt Intrinsics, extensions, and event handlers
Message-ID: <9105311207.AA07116@expire.lcs.mit.edu>
Date: 31 May 91 12:07:51 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 9


    It seems that removing MappingNotify from the list of nonmaskable
    events is a far more serious a change than dispatching additional
    events to handlers for nonmaskable events.

Hardly, given that no implementation of Xt (to my knowledge) has ever
actually supported dispatching of MappingNotify in this way.  (The MIT
implementation sometimes dispatched to one window, that window being
the contents of an uninitialized variable.)