lotus



previous page: 5.8) Why is it a bad idea to draw directly to screen? (Imaging with QuickDraw - Mac Programming)
  
page up: Mac Programming FAQ
  
next page: 5.10) Okay, so how do I get the base address of the screen? (Imaging with QuickDraw - Mac Programming)

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)




Description

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

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)

You have to prepare yourself, and ask these questions:

- Do I want to support all screens, or just 8-bit devices?

- Do I have a few weeks of free time to make it work?

- Do I want to get nasty mail when I break on some hardware and
have to rev the application - even if I may not be able to get
ahold of the hardware that makes it break?

If all you're doing is rendering an image pixel-by-pixel or
line-by-line, maybe you can draw directly into an offscreen
pixMap/GWorld and then CopyBits the entire GWorld to screen?
That will be more compatible, especially if you use the
keepLocal flag when creating the GWorld.

 

Continue to:















TOP
previous page: 5.8) Why is it a bad idea to draw directly to screen? (Imaging with QuickDraw - Mac Programming)
  
page up: Mac Programming FAQ
  
next page: 5.10) Okay, so how do I get the base address of the screen? (Imaging with QuickDraw - Mac Programming)