Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!husc6!endor!olson
From: olson@endor.UUCP
Newsgroups: comp.sys.mac
Subject: Re: What makes programming the Mac difficult?
Message-ID: <2259@husc6.UUCP>
Date: Wed, 10-Jun-87 09:46:19 EDT
Article-I.D.: husc6.2259
Posted: Wed Jun 10 09:46:19 1987
Date-Received: Sat, 13-Jun-87 04:47:13 EDT
References: <869@apple.UUCP> <1499@midas.TEK.COM>
Sender: news@husc6.UUCP
Reply-To: olson@endor.UUCP (Eric Olson)
Organization: Aiken Computation Lab Harvard, Cambridge, MA
Lines: 24

In article <1499@midas.TEK.COM> herbw@midas.UUCP (Herb Weiner) writes:
>2.  I want to do a CopyBits of more than 3K bytes.  I must write a loop to do
>    this.  Why couldn't the toolbox routine include a check for the 3K limit and
>
>    automatically copy the picture in 3K chunks?  (Or better yet, check how
>    much stack space is available, and optimize the copy for the size of the
>    stack.)
> 

I'm not the least bit familiar with this.  I regularly do CopyBits on much
larger bitmaps than 3K.  Perhaps you are talking about the old 3K limit
on the Scrap?  I (and I think everybody else) ignore that, since it was a
sort of arbitrary limit in the documentation only, to keep things working
on 128K Macs.  On an unenhanced (64K ROM) Mac, there may be a real limit
of 32K on the scrap, due to the bug in WriteResource-- but I've never run
into this possible problem, so maybe it doesn't exist.

-Eric
Eric K. Olson	olson@harvard.harvard.edu	harvard!olson
"If the War were fought today, most Americans doubt that we could defeat the
new Japan.  Its atom bombs would be cleaner than ours and come equipped with
"How Did You Like Our Product" postcards that would drop from the sky and
ask questions like "Where did you hear about us?" and "How many in your
family died?"	-John Dvorak