Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!ucsd!ucbvax!dewey.soe.berkeley.edu!oster
From: oster@dewey.soe.berkeley.edu (David Phillip Oster)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Mouse tracking on PICTS
Message-ID: <25636@ucbvax.BERKELEY.EDU>
Date: 15 Aug 88 01:51:16 GMT
References: <496@hudson.acc.virginia.edu>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: oster@dewey.soe.berkeley.edu.UUCP (David Phillip Oster)
Organization: School of Education, UC-Berkeley
Lines: 22

Use the quickdraw bottleneck procedures: 
1.) Inititialize the bottleneck procedures to the standard values.
2.) replace the bottleneck procedures with your own.
Your bottleneck procedures should convert the components of Apple's PICT
to some more tractable representation. (I use a linked list of variable
sized NewHandle() records.)
3.) DrawPicture in this grafport. as the PICT flows passed, your
bottleneck procedures will get called. See the QuickDraw chapter of
Inside Macintosh Don't  forget to handle the semi-standard PicComments (See
the Tech Notes for more information.)
4.) set the bottleneck procedures back to the standard values.
5.) you might as well discard the PICT representation at this point, since
you've got everything you need to replicate it.
6.) when you get a mouse down, search against your linked list
representation of the picture.

Don't forget Color Quickdraw, if the program might run on a mac II. You
may decide to do nothing, but at least you should consider the question.

--- David Phillip Oster            --When you asked me to live in sin with you
Arpa: oster@dewey.soe.berkeley.edu --I didn't know you meant sloth.
Uucp: {uwvax,decvax,ihnp4}!ucbvax!oster%dewey.soe.berkeley.edu