I'm trying to evaluate whether or not I should utility the ImageFormat setting that has been added to NativePDF support. If I understand the description of this setting in the DataWindow Reference pub (page 257), this setting specifies the format of (imbedded) images when the PDF file is created. Since this setting cannot be manipulated in the DataWindow painter, I am manually setting the value in the DataWindow source via Edit Source for the purpose of this evaluation.
I have a DataWindow object (a customer invoice) that contains an image (the company logo; it is in JPG format). The PDF that is produced is *identical*, byte for byte, no matter which PDFNative.ImageFormat setting is used; BMP, JPG, PNG, or GIF.
Since these four image formats are vastly different from one another, it would seem unlikely that the PDF's would be identical when the imbedded image format is changed...therefore this new NativePDF setting looks like it is ignored, and NativePDF appears to actually use only one format, regardless of the setting. Is that what is happening "under the covers"?
It also seems unusual that there is no way to manipulate this setting via the DataWindow Painter.
To summarize:
If I have an embedded image in my DataWindow, the recommended PDFNative.ImageFormat setting is the one that matches the embedded image's format; because this will allow the PDFNative "driver" to, in effect, pass the image through without requiring an image conversion?