I suggest to implement the following feature:
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.