Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!dali!uakari.primate.wisc.edu!brutus.cs.uiuc.edu!psuvax1!psuvm!gfx
From: GFX@psuvm.psu.edu
Newsgroups: comp.sys.mac.hypercard
Subject: Re: lockmouse in supercard?
Message-ID: <90088.145129GFX@psuvm.psu.edu>
Date: 29 Mar 90 19:51:29 GMT
References: <2212.2610f65d@cc.helsinki.fi> <117008@ti-csl.csc.ti.com>
Organization: Penn State University
Lines: 12

In article <117008@ti-csl.csc.ti.com>, martin@m2.csc.ti.com (Steven Martin)
says:
>
>As far as purching recent unhandles messages, I think that "wait until
>the mouse is up" will do what you want, but just for mouse clicks.
>

Wouldn't it trap only the first click?  I personally insert a "repeat
while the mouseClick" loop at the end of scripts that are expected to
take a while to execute.  What is still missing however is a positive
feedback to indicate that the clicks will be purged, similar to the beep
you hear if you try to click outside of a modal dialog.  Stephane