1. Derek Hammonds
  2. PowerBuilder
  3. Wednesday, 13 December 2017 18:56 PM UTC

 

Is there a blurb somewhere detailing what is to be fixed/changed in the upcoming patches regarding the Native PDF funtionality?

As it stands right now this functionality simply isn't usable.  In many, many circumstances the rendering simply doesn't match print preview nor what the ghostscript pdf functionality provides.  We have over 1600 reports in our applications and dozens, if not hundreds, are unusable based on the rendering we see when saving using the NativePDF functionality.  These include, but are not limited to, datawindows with nested reports or datawindows with graphic files embedded in them.

Thanks,

Derek

 

 

 

Accepted Answer
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 13 December 2017 20:06 PM UTC
  2. PowerBuilder
  3. # Permalink

Hi Derek;

     Yes, there are still issues with the rendering from the native PDF feature. More of these issues will be addressed in the PB2017R2 release coming out at the end of this month. The PB2017MR01 release - build 1681 - did address some issues, but certainly not all on our fix list. For now, you might want to return to using GhostScript until you see how the PB2017R2 release improves your App's PDF rendering situation.

Regards ... Chris

Comment
  1. Derek Hammonds
  2. Thursday, 14 December 2017 18:29 PM UTC
Thank you for the replies.



Yes, we are on the latest version.  And we will certainly continue to try the new versions as progress is made with the rendering of NativePDF datawindows.



For now our application is simply too big and we have thousands of reports.  Unless the new nativepdf renders things 99.9% the same as before then it's not worth the bother of migrating and verifying all of our existing reports.  And that is disappointing because ghostscript can be a pain to deploy and maintain.



 



 



 



 

  1. Helpful
There are no comments made yet.
Shenn Sellers Accepted Answer Pending Moderation
  1. Wednesday, 13 December 2017 19:58 PM UTC
  2. PowerBuilder
  3. # 1

Have you upgraded to Build 1681?  That fixed a bunch of issues with the NativePDF functionality. 

Comment
There are no comments made yet.
Roland Smith Accepted Answer Pending Moderation
  1. Thursday, 14 December 2017 00:19 AM UTC
  2. PowerBuilder
  3. # 2

Native PDF is also slower.

Comment
There are no comments made yet.
Gerry Whitmarsh Accepted Answer Pending Moderation
  1. Thursday, 14 December 2017 13:33 PM UTC
  2. PowerBuilder
  3. # 3

... and Native PDF also creates HUGE files!

Comment
  1. Kim Berghall
  2. Friday, 24 August 2018 19:01 PM UTC
It is about the same native vs distill for us. If you stay with Ghostscript, I recommend using a newer version like 9.23. Also if the native creates bigger files it might be that you are embedding jpg files. In that case do this: "DataWindow.Export.PDF.NativePDF.ImageFormat='1'" otherwise the files will be bigger.
  1. Helpful
There are no comments made yet.
Derek Hammonds Accepted Answer Pending Moderation
  1. Monday, 20 August 2018 19:14 PM UTC
  2. PowerBuilder
  3. # 4

Why is this issue listed as 'resolved'.  Practically NONE of the existing issues with NativePDF have been addressed.

 

Native PDF does NOT WORK for us.  It does NOT render things in the same way that ghostscript does.  Period.  End of Story.  There is NO SWITCH to make it render things in the same way as ghostscript.

 

Powerbuilder is a very old legacy product.  We need it to function exactly as it did before or it is useless.  We have THOUSANDS of reports.  Many of them print/render in PDF very BADLY and certainly SLOWLY and NOT AS THEY DID BEFORE.

 

Native PDF is nearly useless.

 

And this is a 'resolved' issue?  I wish I could so easily dismiss real world issues in my job.  Unfortunately, I have to live in the real world and not the 'appeon bubble'.

 

Comment
There are no comments made yet.
Derek Hammonds Accepted Answer Pending Moderation
  1. Monday, 20 August 2018 19:15 PM UTC
  2. PowerBuilder
  3. # 5

 

Native PDF does not work in R2.

 

Native PDF does not work in R3.

 

Native PDF does not work in a box on in a house or in a tree or on a train.

 

Native PDF does not work Sam-I-Am.

 

 

Comment
There are no comments made yet.
Sivaprakash BKR Accepted Answer Pending Moderation
  1. Tuesday, 21 August 2018 13:03 PM UTC
  2. PowerBuilder
  3. # 6

Are all issues resolved in R3, atleast ?   

Comment
There are no comments made yet.
Mark Lee @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 22 August 2018 10:03 AM UTC
  2. PowerBuilder
  3. # 7

Hi Derek,

  1.  Please copy the attached log.ini to the %temp% folder (default directory:C:\Users\appeon\AppData\Local\Temp)and then try to generate PDF file with NativePDF. Log files will be generated in this folder and please provide those generated log files for further analysis.
  2. Kindly please report your PB issue via our support ticketing system to ensure it is being properly received by our tech support and tracked at: https://www.appeon.com/standardsupport/

    Please attach the log files generated (mentioned above) and a test case that can reproduce this issue when opening the ticket. Thanks in advance.

 

Regards,

Mark Lee

Attachments (1)
Comment
There are no comments made yet.
Orlando Alavarez Accepted Answer Pending Moderation
  1. Saturday, 16 May 2020 08:14 AM UTC
  2. PowerBuilder
  3. # 8

Estoy con la version 2019 R2 y sigue mal

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.