Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!genrad!decvax!ucbvax!ucbcad!zen!hoser!bryce
From: bryce@hoser.berkeley.edu (Bryce Nesbitt)
Newsgroups: comp.sys.amiga
Subject: Searching for a workable MENUVERIFY solution
Message-ID: <4145@zen.berkeley.edu>
Date: Sun, 4-Oct-87 10:48:22 EDT
Article-I.D.: zen.4145
Posted: Sun Oct  4 10:48:22 1987
Date-Received: Wed, 7-Oct-87 06:18:19 EDT
Sender: news@zen.berkeley.edu
Reply-To: bryce@hoser.berkeley.edu (Bryce Nesbitt)
Distribution: world
Organization: Center Tapped Solids, Inc.
Lines: 44
Keywords: Intuition, MENUVERIFY, RMBTRAP, Menus, input.device, deadlock
Summary: Looking for an Intuition Guru... (or words to that effect :-)


A person I am working with is producing a program that uses MENUVERIFY. The
"Oh, you mean you can't call DOS with that on." problem was fixed with a
little re-education.  However VERIFY functions still cause a basket full of
headaches.

The application he wants is to use position sensitive right mouse button
selects, Deluxe Paint style.  The current setup uses MENUVERIFY and cancels
the operation if not over the menu bar.  (Can you say "yick!"?)  MENUVERIFY
is a lot of tool and a lot of trouble for a ?simple? need.


It would like to be recoded *not* to use verify.  This does not turn out to
be as easy as it may sound.  I did come up with a way and a test program...
a way for which the word "Kludge" was invented.  Here's the comic story:

Set RMBTRAP.
When a RMB message is received, check the position.
If below the Window's Screen's title bar height handle internal.
Else we just screwed up a menu operation!! Unset RMBTRAP then send a
press-relese pair of RMB events to the input.device.
Reset RMBTRAP after the menu is used.

This works.  In fact, it has a great feel to it.  If the program is too
busy to respond to the pulldown you know immediatly. >Keep holding it, and
the menu will come down when the program is ready to listen<.  Best of all
you can pull the mouse away and do something else (a feature MENUVERIFY
does not offer).  Fantastic!


The theory of operation is ugly, however.  So ugly that the program will
probably be left with verify.  As a long shot another task could handle it.
Neither solution produces end results as nice as the above, or works really
well with what I understand of this particular program's structure.

	What else can be done?
	What are the (truths or) consequences?
	On the ugly index, where does the above fit?

 
|\ /|  . Ack! (NAK, ENQ, SYN)
{o O} . 
 (") 	bryce@hoser.berkeley.EDU -or- ucbvax!hoser!bryce
  U	How can you go back if you have not yet gone forth?