Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!mcvax!kth!draken!tut!santra!kampi.hut.fi!jmunkki
From: jmunkki@kampi.hut.fi (Juri Munkki)
Newsgroups: comp.sys.mac.programmer
Subject: Re: TrackButton()
Keywords: Anyone want to help polish some code?
Message-ID: <23239@santra.UUCP>
Date: 27 Jun 89 10:24:59 GMT
References: <128@dbase.UUCP>
Sender: news@santra.UUCP
Reply-To: jmunkki@kampi.hut.fi (Juri Munkki)
Organization: Helsinki University of Technology, Finland
Lines: 34

In article <128@dbase.UUCP> awd@dbase.UUCP (Alastair Dallas) writes:
<Boolean TrackButton(button)
<Rect *button;
<{
<	Boolean		wasIN = FALSE;
<	Point		mouse;
<	while (StillDown())
<	{ 	GetMouse(&mouse);
<		if (PtInRect(mouse, button) != wasIN)
<			{	InvertRect(button);
<				wasIN = !wasIN;
<			}
<		}
<	if (wasIN) 	InvertRect(button);
<	return (wasIN);
<}	/* TrackButton */
<By the way, I'm not missing something obvious, am I?  I mean, the Control
<Manager seems like a lot of overkill to handle a simple (and custom)
<button or two.  Should I write a CDEF for this?  Comments are welcome...

What if the user quickly presses and releases the mouse button on the
control and then moves the mouse away from the button area. Your routine
does not detect this. You should use GetNextEvent to find when the button
comes up and where it comes up. Since GetNextEvent returns the mouse
location, you can remove the GetMouse too. 

Your code is not compatible with Quickeys. I used to program this way
(take a look at my Mandelbrot DA source), but discovered that since it
does not depend on mouseUp events, it doesn't work with QuicKeys.

_._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._
|     Juri Munkki jmunkki@hut.fi  jmunkki@fingate.bitnet        I Want   Ne   |
|     Helsinki University of Technology Computing Centre        My Own   XT   |
^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^