Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!bbn!usc!apple!claris!jazzman
From: jazzman@claris.com (Sydney R. Polk)
Newsgroups: comp.sys.apple
Subject: Re: IIGS programming question
Message-ID: <10336@claris.com>
Date: 24 Jun 89 01:13:10 GMT
References: <9607@boulder.Colorado.EDU>
Organization: Claris Corporation, Santa Clara CA
Lines: 21

From article <9607@boulder.Colorado.EDU>, by hartkopf@tramp.Colorado.EDU (HARTKOPF JEFFREY M):
> 
> Another question about IIGS toolbox programming:  In a program I'm writing
> I have a small window that opens and then closes again as soon as the user
> presses the mouse button (anywhere on the screen).  (By the way, I don't
> want to use a dialog box for this purpose.)  That part works fine, but when
> the program gets back to the main event loop it interprets that mouse press
> as part of the event queue and acts accordingly, which I don't want.  What I
> want it to do is use that mouse press to close the window, and then NOT add
> it to the event queue.  Is there some way to do this?  Thanks a lot.

You mean you are not using the event to draw the window?  What are you doing,
itercepting mouse interrupts directly?

If you draw when you get the event, then this problem should go away, no?

-- 
Syd Polk           | Wherever you go, there you are.
jazzman@claris.com | Let the music be your light.
GO 'STROS!         | These opinions are mine.  Any resemblence to other
GO RICE!           |  opinions, real or fictitious, is purely coincidence.