Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!rpi!uupsi!sunic!tut!santra!kampi.hut.fi!jmunkki
From: jmunkki@kampi.hut.fi (Juri Munkki)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Need help creating a Quickdraw picture
Message-ID: <1990Jun1.173103.11808@santra.uucp>
Date: 1 Jun 90 17:31:03 GMT
References: <2205@dftsrv.gsfc.nasa.gov> <7358@jarthur.Claremont.EDU>
Sender: news@santra.uucp (Cnews - USENET news system)
Reply-To: jmunkki@kampi.hut.fi (Juri Munkki)
Organization: Helsinki University of Technology
Lines: 22

In article <7358@jarthur.Claremont.EDU> mwilkins@jarthur.Claremont.EDU (Mark Wilkins) writes:
>In article <2205@dftsrv.gsfc.nasa.gov> seiler@amarna.gsfc.nasa.gov writes:
>>CopyBits(&(windPtr->portBits), &(windPtr->portBits),
>>         &(windPtr->portRect), &(windPtr->portRect), srcCopy, NULL);
>
>
>  CopyBits just doesn't like it if the source and destination bitmaps are
>the same, and I THINK it doesn't like it if the same rectangle data
>structure is passed in both places.

I don't know what 'seiler' is trying to do here, but actually I seem to
remember that only the 64KB ROMs had quickdraw that didn't like copybitsing
within the same bitmap. Giving the same rectangle is fine with any version
of quickdraw.

I have used a similar statement to copy the contents of a window to a picture
definition (later to be copied into the scrap).

   ___________________________________________________________________________
  / Juri Munkki	    /  Helsinki University of Technology   /  Wind  /   HP S /
 / jmunkki@hut.fi  /  Computing Center Macintosh Support  /  Surf  /   48 X /
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~