Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!wuarchive!usc!rutgers!cbmvax!peter
From: peter@cbmvax.commodore.com (Peter Cherna)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: RMB question
Message-ID: <21506@cbmvax.commodore.com>
Date: 13 May 91 15:53:35 GMT
References: <1991May8.155337.5049@zorch.SF-Bay.ORG> <21412@cbmvax.commodore.com> <1991May11.010739.24499@zorch.SF-Bay.ORG>
Reply-To: peter@cbmvax.commodore.com (Peter Cherna)
Organization: Commodore-Amiga, Inc.  West Chester, PA.
Lines: 22

In article <1991May11.010739.24499@zorch.SF-Bay.ORG> mike@zorch.SF-Bay.ORG (Mike Smithwick) writes:
>Trouble with MENUVERIFY is that I get only a single message. I need to know
>both MENUDOWN and MENUUP events which MENUVERIFY won't give.

Crudely speaking, MENUVERIFY corresponds to MENUDOWN and MENUPICK to
MENUUP.

Normally, if you need to hear MENUUP and MENUDOWN, you don't also
need to hear MENUPICK.  That is to say, your program would have two
states, which the user might enter explicitly or implicitly (eg.
mouse position in DPaint).

You can set or clear RMBTRAP atomically to effect the state change.

>mike

     Peter
--
Peter Cherna, Operating Systems Development Group, Commodore-Amiga, Inc.
{uunet|rutgers}!cbmvax!peter    peter@cbmvax.commodore.com
My opinions do not necessarily represent the opinions of my employer.
"If all you have is a hammer, everything looks like a nail."