lotus



previous page: 5.7) How do I find the current depth of the screen? (Imaging with QuickDraw - Mac Programming)
  
page up: Mac Programming FAQ
  
next page: 5.9) But I really need to do it. I can't make my animation into a QuickTime movie, and CopyBits is too slow, even when syncing to the screen retrace and with my source GWorld aligned properly. (Imaging with QuickDraw - Mac Programming)

5.8) Why is it a bad idea to draw directly to screen? (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.8) Why is it a bad idea to draw directly to screen? (Imaging with QuickDraw - Mac Programming)

Because of several reasons:

- You will be incompatible with future display hardware.

- You will be incompatible with some present-day display
hardware, such as Radius Pivots and PowerBook color screens.

- You have to think about a lot of things; testing it all on
your own machine is not possible and the chances of crashing are
great.

- You will be incompatible with future hardware where devices
may live in some unaccessible I/O space.

 

Continue to:















TOP
previous page: 5.7) How do I find the current depth of the screen? (Imaging with QuickDraw - Mac Programming)
  
page up: Mac Programming FAQ
  
next page: 5.9) But I really need to do it. I can't make my animation into a QuickTime movie, and CopyBits is too slow, even when syncing to the screen retrace and with my source GWorld aligned properly. (Imaging with QuickDraw - Mac Programming)