mtr@mentor.cc.purdue.edu (Michael Rowan) (04/26/89)
I was under the impression that we could use event.xany for any of the first 5 values. In almost every case this is true. Except with the Mapping, configure, create and destroy events. Why did you switch the parent and window fields so that : event.xany.window != event.xmaprequest.window ^^^^^^^^^^^ this or the others i mentioned Is there a good reason that I am missing? mtr
rws@EXPO.LCS.MIT.EDU (04/26/89)
event.xany.window != event.xmaprequest.window ^^^^^^^^^^^ When an event is received by the client, you want to be able to use event.xany.window to correctly dispatch the event. In the case of the MapRequest event, the window that you want to use for dispatching is in fact the "parent" field in the event, not the field named "window" in that event. I admit this is confusing, but I believe the events are structured correctly.