When the segment per width property is greater than 1 the report attempts to display the total page width on one page. This is in the print preview of the preview tab in the report designer. Even worse, the report will print under these display conditions.
I provided a video of the problem utilizing an example from your Online Live Demo. The first part of the video is how I created the report. The second part shows the problem when the print icon is selected and the default option is chosen from the Print Dialogue. The last part of the video is what we desire. When the Print to PDF option is selected the preview does not attempt to display the full report's page width on one page. Thus, the result also means that the report will print correctly. We would like the default option to behave like the Print to PDF option.
Is there a solution to this currently existing in Stimulsoft?
Video - http://screencast.com/t/l4QPntym
Print Preview and Printed Reports scales to fit 1 page width
-
- Posts: 9
- Joined: Wed Nov 28, 2012 7:59 pm
Re: Print Preview and Printed Reports scales to fit 1 page w
Hello,
We have reproduced the error, added to the queue for fixing.
Thank you.
We have reproduced the error, added to the queue for fixing.
Thank you.
-
- Posts: 9
- Joined: Wed Nov 28, 2012 7:59 pm
Re: Print Preview and Printed Reports scales to fit 1 page w
Hello,
We just updated to Stimulsoft Web 2013.2.1700 and were hoping this error was fixed. Upon testing the error still exists. Also in your online demo for Web that error is present. Is there any timeline for fixing the issue?
Best,
Jordan
We just updated to Stimulsoft Web 2013.2.1700 and were hoping this error was fixed. Upon testing the error still exists. Also in your online demo for Web that error is present. Is there any timeline for fixing the issue?
Best,
Jordan
Re: Print Preview and Printed Reports scales to fit 1 page w
Hello,
We have raised the priority of this task, the problem should be solved to the next prerelease build from 8 November.
Thank you.
We have raised the priority of this task, the problem should be solved to the next prerelease build from 8 November.
Thank you.