Why does Alpha5 v5 render photos different between a form and a report even though the image file reference field settings are the same? This presents a big quality problem of cross hatching with some photos (ones that the origional is wider than tall), both in display (print preview) and print out of the report.
I want to know how I can solve this problem or work around it if someone has already solved this.
I have posted 4 messages total and attached one screen capture file illistrating the problems to each for viewing purposes.
Explanation:
The origional photo named OrigionalOFA2888.jpg is 1.62" w x 1.24"h x 150 pixels per inch (resolution). This translates into 243 pixels x 186 pixels x 150 pixels per inch (resolution). and is attached to this message.
I have a form with an image file reference field on it. The field size is 2.5" x 2.5". In the setup for the field on the form the Display Mode is: Absolute. The screen capture photo named AbsoluteImageForm is of the above sized photo displayed in the image file reference field on the form and looks normal.
The report has an image file reference field on it. The field size is 2.5" x 2.5". I have two screen captures, one of the photo with the field Display mode set as Absolute, and the other set as Stretch for the display mode.
The image named AbsoluteImageReport is captured from the report with the image file reference field set to absolute. You can see it is way smaller than either it's origional size or the absolute size displayed on the form.
The image named BestFitImageReport is captured from the same report, with the image file reference field Display mode set to Best Fit. As the capture shows there are black lines cross hatching the photo. This is not acceptable in on screen display and photos with crosshatching also print out with the black lines (cross hatch) showing.
Making the origional image larger or smaller does not improve the display in a report. In fact it makes it worse with more cross hatching.
Please see the other 3 posts for the additional files. If it is better that I post all the files in a zip file I can do that.
Thanks,
Phil DeGruy
I want to know how I can solve this problem or work around it if someone has already solved this.
I have posted 4 messages total and attached one screen capture file illistrating the problems to each for viewing purposes.
Explanation:
The origional photo named OrigionalOFA2888.jpg is 1.62" w x 1.24"h x 150 pixels per inch (resolution). This translates into 243 pixels x 186 pixels x 150 pixels per inch (resolution). and is attached to this message.
I have a form with an image file reference field on it. The field size is 2.5" x 2.5". In the setup for the field on the form the Display Mode is: Absolute. The screen capture photo named AbsoluteImageForm is of the above sized photo displayed in the image file reference field on the form and looks normal.
The report has an image file reference field on it. The field size is 2.5" x 2.5". I have two screen captures, one of the photo with the field Display mode set as Absolute, and the other set as Stretch for the display mode.
The image named AbsoluteImageReport is captured from the report with the image file reference field set to absolute. You can see it is way smaller than either it's origional size or the absolute size displayed on the form.
The image named BestFitImageReport is captured from the same report, with the image file reference field Display mode set to Best Fit. As the capture shows there are black lines cross hatching the photo. This is not acceptable in on screen display and photos with crosshatching also print out with the black lines (cross hatch) showing.
Making the origional image larger or smaller does not improve the display in a report. In fact it makes it worse with more cross hatching.
Please see the other 3 posts for the additional files. If it is better that I post all the files in a zip file I can do that.
Thanks,
Phil DeGruy
Comment