lotus



previous page: 5.1) Why is CopyBits so slow? (Imaging with QuickDraw - Mac Programming)
  
page up: Mac Programming FAQ
  
next page: 5.3) What is the fastest way to set one pixel? (Imaging with QuickDraw - Mac Programming)

5.2) Why is CopyBits still too slow? (Imaging with QuickDraw - Mac Programming)




Description

This article is from the Mac Programming FAQ, by Jon Watte h+@austin.metrowerks.com with numerous contributions by others.

5.2) Why is CopyBits still too slow? (Imaging with QuickDraw - Mac Programming)

Because there is always some overhead involved in calling QuickDraw;
you have the trap dispatcher, clipping checks, and checking whether the
CopyBits call is being recorded in a PICT handle (if you called
OpenPicture)

If you can't live with this, look at 4.8 below, but PLEASE try and make
CopyBits work, and retain the CopyBits code in your application, so
users with special monitors (accellerator cards, PowerBook color
screens, Radius Pivot screens) can still play your game. (non-game
applications don't need more speed than CopyBits can give at its max.
Promise!)

 

Continue to:















TOP
previous page: 5.1) Why is CopyBits so slow? (Imaging with QuickDraw - Mac Programming)
  
page up: Mac Programming FAQ
  
next page: 5.3) What is the fastest way to set one pixel? (Imaging with QuickDraw - Mac Programming)