🚀 go-pugleaf

In article <908@ur-tut.UUCP> broe@tut.cc.rochester.edu.UUCP (Eric Brown) writes:
>We have the same problem - though, we have narrowed down the problem a little
>more.  The problem seems to be either finder 5.5 or greater or system 4.2
>or greater running on anything less than a Mac II.  I know personally, I am
>using finder 6.0 with system 4.2 on a 1meg SE and have the same problem.
>The problem, I believe, is not with Word, it is the program you ran before-
>Word.  (perhaps some INITed file)  Here at work, we are developing an
>application for the Mac with Lightspeed C.  Before we run the application
>(either compilied or in LSC shell), double clicking works as normal.  After
>running it only once, double clicking ceases to work in finder.  (just as
>you describe above)  We can't seem to pinpoint the problem except that the
>problem ceases when we use a lesser system and finder (as you said above).
>Another program that does the same thing as our application does is the
>stand alone MacMan application (not the DA).  Please note that this problem
>does not aflict Mac IIs - double clicking always works.

I'm sorry, I don't mean to be writting to myself, but apperently, my boss
found the double-click problem.  I just want to explain what the bug is for
any other developers experiencing the same problem.  It happens to be with 
new finders, the eventmask an a source skeleton that apple supplys for
applications.  Appearently, finder 6.0 does not resent the eventmask when
an application ends (MultiFinder does).  To repair applications that
misbehave in the way described above, you should reset the eventmask before
exiting an application.  (or don't mask out mouseUp events at the beginning
of your application.)

					Eric.