Page 1 of 2

Viewer vs. printing...

Posted: Tue Sep 13, 2011 7:10 am
by LukasT
I see a lot of differences between Viewer preview content and content on paper (PDFCreator output)...
... for example output of your PDF export and printing output from PDFCreator... see attached pdf files.

...and I have found diferences in functionality of each type of text trimming properties in WpfDesigner and WinForm Designer... try for example "Character"....
Try to open report01.mdc in Wpf and WinForm Viewer... there are critical differences.

Viewer vs. printing...

Posted: Wed Sep 14, 2011 7:55 am
by HighAley
LukasT wrote:I see a lot of differences between Viewer preview content and content on paper (PDFCreator output)...
... for example output of your PDF export and printing output from PDFCreator... see attached pdf files.
Unfortunately, we don't have PDFCreator utility and we can't check it. But in other programs (AdobePDF, doPdf, OneNote) and on physical printers there are no problems.
By the way there are several users inform us about problems with PDFCreator. But we don't know what is the reason.
LukasT wrote:...and I have found diferences in functionality of each type of text trimming properties in WpfDesigner and WinForm Designer... try for example "Character"....
Try to open report01.mdc in Wpf and WinForm Viewer... there are critical differences.
'
WinForms and WPF use different methods of text output, therefore strings have different length. When the 'Word Wrap' property is true the text wraps what you can see in WinForms.
Therefore you must render reports for each viewer separately. Please, for WinForms use Render() method and for WPF use RenderWithWpf() method.

Thank you.

Viewer vs. printing...

Posted: Wed Sep 14, 2011 8:40 am
by LukasT
Unfortunately, we don't have PDFCreator utility and we can't check it. But in other programs (AdobePDF, doPdf, OneNote) and on physical printers there are no problems.
By the way there are several users inform us about problems with PDFCreator. But we don't know what is the reason.
... I can't say why, but even output from physical printer is wrong... see text on top of page: číslo 11PTZ0100000002 .... in viewer it is correct, in PDF export correct but on printer the number is outside of border... do you see the same?
WinForms and WPF use different methods of text output, therefore strings have different length. When the 'Word Wrap' property is true the text wraps what you can see in WinForms.
Therefore you must render reports for each viewer separately. Please, for WinForms use Render() method and for WPF use RenderWithWpf() method.


... but rendering with correct method is not solving diference between for example trimming types... I don't wont to see in wpf Viewer text with three dots ellipsis and in WinForm Viewer with character trimming.

Viewer vs. printing...

Posted: Thu Sep 15, 2011 1:26 pm
by Ivan
Hello,
I can't say why, but even output from physical printer is wrong... see text on top of page: číslo 11PTZ0100000002 .... in viewer it is correct, in PDF export correct but on printer the number is outside of border... do you see the same?
Please try to set the TextQuality property of the problem textboxes to WYSIWYG.
... but rendering with correct method is not solving diference between for example trimming types... I don't wont to see in wpf Viewer text with three dots ellipsis and in WinForm Viewer with character trimming.
Unfortunately, the TextTrimming enumeration in WPF contain only three members - None, CharacterEllipsis and WordEllipsis.
Therefore we cannot support Character and Word trimming in Wpf, only in WinForms.

Thank you.

Viewer vs. printing...

Posted: Fri Sep 16, 2011 3:41 am
by LukasT
Please try to set the TextQuality property of the problem textboxes to WYSIWYG.
In WinForm designer this property is solution, but what in WPF? There is no property TextQuality...
Unfortunately, the TextTrimming enumeration in WPF contain only three members - None, CharacterEllipsis and WordEllipsis.
Therefore we cannot support Character and Word trimming in Wpf, only in WinForms.
... but what is problem to write your own character and word trimming? :-)


Viewer vs. printing...

Posted: Mon Sep 19, 2011 5:00 am
by HighAley
Hello.
LukasT wrote:
Please try to set the TextQuality property of the problem textboxes to WYSIWYG.
In WinForm designer this property is solution, but what in WPF? There is no property TextQuality...
We'll think about this feature.
LukasT wrote:
Unfortunately, the TextTrimming enumeration in WPF contain only three members - None, CharacterEllipsis and WordEllipsis.
Therefore we cannot support Character and Word trimming in Wpf, only in WinForms.
... but what is problem to write your own character and word trimming? :-)
There is a very hard technical problem and, unfortunately, we do not have plans to develop this feature.

Thank you.

Viewer vs. printing...

Posted: Tue Sep 20, 2011 3:13 am
by LukasT
We'll think about this feature.
Be fast in this case, please... because I thing this problem is critical for us. Our customers have in system hunderts reports which have potentionally problem in this case. Even for you is priority to have the same content on paper and on screen - „What you see is what you get“.
Thank you and I am waiting for solution.

Viewer vs. printing...

Posted: Tue Sep 20, 2011 4:36 pm
by Ivan
Hello,

In the next prerelease build we will add the new static property StiOptions.Wpf.ShowAllPropertiesInWpf, by default false.
Please set this property to true.

Thank you.

Viewer vs. printing...

Posted: Thu Sep 29, 2011 6:01 am
by LukasT
Thank you Ivan,
it looks alright now...
Have a nice day ;-)

Viewer vs. printing...

Posted: Thu Sep 29, 2011 6:14 am
by HighAley
Hello.

We are always glad to help you.
Have a nice day!

Thank you.