Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!rutgers!usc!snorkelwacker!bloom-beacon!SHAMASH.MCRCIM.MCGILL.EDU!mouse From: mouse@SHAMASH.MCRCIM.MCGILL.EDU (der Mouse) Newsgroups: comp.windows.x Subject: Re: Propagation of Device Event? Message-ID: <9007140652.AA07301@shamash.McRCIM.McGill.EDU> Date: 14 Jul 90 06:52:23 GMT Sender: daemon@athena.mit.edu (Mr Background) Organization: The Internet Lines: 49 > Assuming window tree hierarchy in the server is: > root > / | \ > c1 A B > / > c2 > and > pointer is in c2, > button pressed, > no active/passive grabs, > no do-not-propagate masks, > just normal event distribution in the server. Well, grabs and do-not-propagate masks are part of normal event distribution, but aside from that.... > the screen appearance is: > --------------------------- > | root | > | ----------------- | > | | A | | > | -------------- | | > | | B | | | > | | |----- | > | | ---- |c1 | | > | | |c2| | | | > | | |x | | | | > | | ---- | | | > | -------------- | | > | | -------------- | > | | | | > | ----------------- | > | | > --------------------------- This is not possible. Given your hierarchy above, c2 can't be in front of B unless c1 also is. (All the children of a window W always have the same relationship as W in the global front-to-back stacking order relative to any other window X which is neither W nor a child of W. In this case, W is c1, the child is c2, and X is B.) If, however, c1 in your picture is raised to in front of B, all the answers you gave to your own questions are (according to my own understanding of event distribution, which may well be flawed) correct. der Mouse old: mcgill-vision!mouse new: mouse@larry.mcrcim.mcgill.edu