Barry.Chern@f200.n226.z1.FIDONET.ORG (Barry Chern) (08/12/89)
I don't know the answer to this for sure, but I have an intuitive idea about it. The events, mouseclicks etc., still get queued up. But instead of executing after you exit the handler, the "wait" causes the handler to wait while they "execute" with no effect, behind the scenes. Since they are queued up, there's no question of the various mouseUps along the way being interpreted as "the mouse is up" since the computer will aready know that it went down again. Only when there is no further mouseDown will the handler stop waiting. -- Barry Chern via cmhGate - Net 226 fido<=>uucp gateway Col, OH UUCP: ...!osu-cis!n8emr!cmhgate!200!Barry.Chern INET: Barry.Chern@f200.n226.z1.FIDONET.ORG