1. The bitmap object and HTML object do not display correctly unless you do the following:
Use the "best fit" or "stretch" or "best fit" display options. However if the image is set to a print resolution of 300 or 600 dpi it will be grainy. But if you do this Image must have a printer resolution of 300dpi or higher. 200dpi looked ok, 300 or 600dpi looked the best, but I could not tell the difference between the two when the report was displayed on the screen as a PDF.
If the images are set at a screen dpi such as 72dpi, it will look good on the screen if displayed using the "absolute" value, but when the report is displayed on the screen as a PDF it will shrink dramatically.
If you use the "stretch" or "best fit" display options with the lower dpi it will look OK on the screen and jaggy when the report is displayed on the screen as a PDF.
2. Using the HTML object will not give you the "stretch" or "best fit" display options. Also you are limited to displaying one image only. Adding multiple images will display the first image, and drop the others. Additionally, to get the best image quality you will not be able to see the images in the report writer, both in editing and preview modes. When you go into the the HTML editing mode you will see the images, but the will they will be large, and then disappear when you close the editor.
3. the HTML object does not support a full contingent of CSS styles.
For example in the report that I am building it does not support the following:
Float - needed to do complex alignments. It displays correctly in the HTML editor, the report writer and in preview, but fails when published.
Rotation - Fails in the report writer, in preview, and when published.
Where does the HTML object shine. In displaying text objects that need to shrink and grow. Much better than the native capacity. Also, in the ability to format the text as this can all be handled via in page CSS styles.
4. ROTATED TEXT - I use a graphics program to rotate and then export it as a png file (300dpi). I then import it into the report using the Bitmap Object and use the "best fit" setting.
Why not use the text object and use the rotation setting? If you need to do -90 (270) degree rotation. It does not render correctly.
5. The HTML object sometimes stops displaying in the report writer and in preview. To overcome this I sometimes can make changes to the HTML code, other times I have to shrink the HTML object in the report writer, save, and then put it back to the normal dimensions that I need.
Regards,
Use the "best fit" or "stretch" or "best fit" display options. However if the image is set to a print resolution of 300 or 600 dpi it will be grainy. But if you do this Image must have a printer resolution of 300dpi or higher. 200dpi looked ok, 300 or 600dpi looked the best, but I could not tell the difference between the two when the report was displayed on the screen as a PDF.
If the images are set at a screen dpi such as 72dpi, it will look good on the screen if displayed using the "absolute" value, but when the report is displayed on the screen as a PDF it will shrink dramatically.
If you use the "stretch" or "best fit" display options with the lower dpi it will look OK on the screen and jaggy when the report is displayed on the screen as a PDF.
2. Using the HTML object will not give you the "stretch" or "best fit" display options. Also you are limited to displaying one image only. Adding multiple images will display the first image, and drop the others. Additionally, to get the best image quality you will not be able to see the images in the report writer, both in editing and preview modes. When you go into the the HTML editing mode you will see the images, but the will they will be large, and then disappear when you close the editor.
3. the HTML object does not support a full contingent of CSS styles.
For example in the report that I am building it does not support the following:
Float - needed to do complex alignments. It displays correctly in the HTML editor, the report writer and in preview, but fails when published.
Rotation - Fails in the report writer, in preview, and when published.
Where does the HTML object shine. In displaying text objects that need to shrink and grow. Much better than the native capacity. Also, in the ability to format the text as this can all be handled via in page CSS styles.
4. ROTATED TEXT - I use a graphics program to rotate and then export it as a png file (300dpi). I then import it into the report using the Bitmap Object and use the "best fit" setting.
Why not use the text object and use the rotation setting? If you need to do -90 (270) degree rotation. It does not render correctly.
5. The HTML object sometimes stops displaying in the report writer and in preview. To overcome this I sometimes can make changes to the HTML code, other times I have to shrink the HTML object in the report writer, save, and then put it back to the normal dimensions that I need.
Regards,