• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: handling of huge bitmaps, incremental saving?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: handling of huge bitmaps, incremental saving?


  • Subject: Re: handling of huge bitmaps, incremental saving?
  • From: Robert Clair <email@hidden>
  • Date: Fri, 2 Jan 2004 10:34:13 -0500

> Cocoa does not handle saving as strips (or tiles) at this time, but the
> TIFF format does and so does the tifflib. You will probably have to
> use that directly. It's not as comfy as Cocoa, but pretty
> straightforward.

Drawing your image in strips or tiles by setting your context
appropriately or
calling the image's drawRect method with the correct rectangle, getting
the pixels and
using them to write a TIFF strip with libtiff works just fine. (At
least for me :-) ).
You should make sure that the size of the tile in the floating point
view space is an
exact multiple of the view space size of a pixel. This will help keep
you from seeing any
banding artifacts. I haven't seen any, even with quite complicated
Bezier paths and ones that
were designed, as a test, to be artifact prone (line crossing the strip
boundary at a very
low angle, etc). The last strip can be a partial strip.


............Bob
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

  • Prev by Date: Re: Double-Click Column Header??
  • Next by Date: Allocation during awakeFromNib
  • Previous by thread: Re: handling of huge bitmaps, incremental saving?
  • Next by thread: Fun GDB tricks
  • Index(es):
    • Date
    • Thread