Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!asuvax!stjhmc!p88.f15.n300.z1.fidonet.org!Lawson.English
From: Lawson.English@p88.f15.n300.z1.fidonet.org (Lawson English)
Newsgroups: comp.sys.mac.programmer
Subject: Faster than CopyBits?
Message-ID: <6552.27F82A29@stjhmc.fidonet.org>
Date: 28 Mar 91 14:44:56 GMT
Sender: ufgate@stjhmc.fidonet.org (newsout1.26)
Organization: FidoNet node 1:300/15.88 - Tucson Apple Core, Tucson AZ
Lines: 24

2fmlcalls@kuhub.cc.ukans.edu writes in a message to All

2>  What is the quickest way to blast bits to the screen? 
2> I'm aware of CopyBits long and shortcomings and I thought (know) 
2> there must be a better way

I don't know about screen vs off-screen, but CopyBits is pretty well optimized:
on a Plus machine (the last I Mac-Nosy-ed), CopyBits spends the greatest part
of its time in a loop using 16 move.w instructions. I would *assume* that on
32 bit machines, there is optimizatiion to check for long words, but if not,
then, assuming a long word boundry, one might use 16 or 32 (more then that is
reaching the point of diminishing returns if I recall correctly from my Apple
II graphic days and if the instruction set timing is ball-parkish) move.l's
to blast your bits around. It wouldn't know the first thing about regions and
such, but you said that you didn't need them. Also, this only works in black
and white...


Lawson
 

--  
Uucp: ...{gatech,ames,rutgers}!ncar!asuvax!stjhmc!300!15.88!Lawson.English
Internet: Lawson.English@p88.f15.n300.z1.fidonet.org