Path: utzoo!attcan!uunet!cs.utexas.edu!samsung!uakari.primate.wisc.edu!dali!ogicse!emory!mephisto!mcnc!ecsgate!ecsvax!utoddl
From: utoddl@uncecs.edu (Todd M. Lewis)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Programming differences between 2.0 and 1.3
Message-ID: <1990May30.191227.4923@uncecs.edu>
Date: 30 May 90 19:12:27 GMT
References: <8aDCJNG00WB7Q_wUMI@andrew.cmu.edu> <11417@cbmvax.commodore.com> <8790@sbcs.sunysb.edu> <5675@sugar.hackercorp.com>
Organization: UNC Educational Computing Service
Lines: 26


Well, here's one difference I've found on a developer-friend's
1.4beta: the ENDGADGET flag on a boolean REQGADGET is no
longer sufficient to get a requester to go away.  Adding
another flag (e.g., RELVERIFY) makes it work.  I don't know
if this has been fixed in the 2.0beta, but it worked fine
in 1.2 and 1.3.  Lots of programs that open requesters
will wait forever for a REQCLEAR message that will never
come if this isn't fixed.  I may get to try it on a
2.0beta later this week.

Another problem with the 1.4beta has to do with MENUVERIFY
and how the right button is handled.  One of my programs
does something, er, special, with the right button if the
pointer is over a certain part of the window.  It does this
special thing over and over until the button is released.
Under 1.4beta, it only does it once and then the menu
gets activated even though I sent back MENUCANCEL to the
MENUVERIFY message.  Again, I hope to test this with my
developer-friend's 2.0beta sometime this week.
_____        
  |      Todd M. Lewis            Disclaimer: If you want my employer's
  ||\/|  utoddl@ecsvax.uncecs.edu             ideas, you'll have to
  ||  || utoddl@ecsvax.bitnet, @unc.bitnet    _buy_ them. 
   |  || utoddl@next1.mscre.unc.edu 
       |___   ("Prgrms wtht cmmnts r lk sntncs wtht vwls." --TML)