Path: utzoo!attcan!uunet!ncrlnk!ncr-sd!hp-sdd!hplabs!decwrl!labrea!rutgers!att!chinet!saj
From: saj@chinet.chi.il.us (Stephen Jacobs)
Newsgroups: comp.sys.atari.st
Subject: Re: button events.  Wanting to wait for either one or two clicks.
Summary: Can someone explain peculiarities of button events?
Keywords: evnt_button, evnt_multi, Laser C
Message-ID: <6982@chinet.chi.il.us>
Date: 22 Nov 88 15:18:50 GMT
References: <1988Nov19.180454.563@gpu.utcs.toronto.edu> <7632@pasteur.Berkeley.EDU>
Organization: Chinet - Chicago Public Access UNIX
Lines: 7

I'd like to tag an old question onto this discussion of button sensing: some
mouse sensing calls leave the machine in an unexpected state.  In particular,
after using a call (was it vq_mouse()?) to interrogate the mouse button state
in a loop, an evnt_multi() waiting for a mouse event exits immediately, even
if a fairly long time elapses between the completion of the loop and the call
to evnt_multi().  Does this sound familiar to anyone?  Would you care to
explain the scope of this peculiarity, and suggest a remedy?