I must be doing something stupid. Where is the Tarif and Availability section.
carlfromtucson
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
This is a Macintosh app. The image is composed in Pages, exported as a pdf, imported into Preview, and exported as either a png or a jpg. The images are either 1448 × 1589 or 2880 × 1800.
Polyphonic:
Thank you for your prompt reply. It caused me to think more deeply about the issue. I have other obligations right now. I'll comment substantively tomorrow after I have thought more on the issue.
I am loading the archived data for a NSOutlineView. My OutlineItems are stored in a tree. Each OutlineItem contains a NSMutableArray (Children). This array contains the children for that OutlineItem. The problem turns out to be with one OutlineItem. Its Children' is shown as an __NSPlaceholderArray when I debug. Apparently it was archived that way due to a bug. Right now, I'm looking for a way to detect items with such an array and delete the item. I'll save the bug itself for later.
A map snapshot is all I would need. Before I spend a lot of work leaning mapkit (which seems pretty dense), I would like to know if a big snapshot would be practical. Would an extreme example like a 10 kilometer square snapshot with 1 meter pixels be feasible (100 million pixels).