Split large images into several areas in the preview file.
A typical use case might be:
Several of our customers use page size images to print their entire letter layout with a logo in the header and, for example, the bank details in the footer.
Since we are working with a 32-bit application, this sometimes leads to OutOfMemory exceptions and similar problems when loading the preview file with the PreviewFile class.
I have found that such images are output as a single EMF record, which means that a memory block of approx. 140 MB is required for an A4 page and an image resolution of 600 DPI.
My suggestion would be to split these images up to use smaller blocks of memory.
Sounds to me like you’d be better off splitting the letter template itself into multiple areas, or using a PDF. Here’s an article covering the topic:
Artificially splitting large images into smaller ones might lead to problems for printers or other export formats (hairlines between sections, no common selection, irritation for screen readers/accessibility features). I don’t think we’re prepared to tackle this.
Hello Jochen,
We always recommend that our users use small images or PDFs as letterhead. However, we’ve switched to 64-bit anyway, so it doesn’t matter anymore.
