Looking for feedback on the Carya PDF toolkit.

[beuvink]

FYI Fonts are now fixed indeed. Now also noticing that fonts were not correct in pdf, this is also fixed now. 👍

[Rafals10]

Hello,

I have implemented this PDF Toolkit into the project of test machine software to automatic report generation after test finish. On the project level it works fine (great toolkit!). My problem appears when I build an executable file. There is no error, but the PDF file is not created after test. I suppose that I need to add something in the Build properties. I have tried to add there PDF Toolkit folder, but without a success. I have found in network that standard VIs which use MS Word for PDF generation require a lvclass file in the build, but in my case there is no Word need and no lvclass file.

Could you please explain me how should I prepare my build to have a working Toolkit in the exe file?

Thanks in advance!

Rafał

[wiebe@CARYA]

---

@Rafals10 wrote:

Hello,

I have implemented this PDF Toolkit into the project of test machine software to automatic report generation after test finish. On the project level it works fine (great toolkit!). My problem appears when I build an executable file. There is no error, but the PDF file is not created after test. I suppose that I need to add something in the Build properties. I have tried to add there PDF Toolkit folder, but without a success. I have found in network that standard VIs which use MS Word for PDF generation require a lvclass file in the build, but in my case there is no Word need and no lvclass file.

Could you please explain me how should I prepare my build to have a working Toolkit in the exe file?

---

You shouldn't need to add anything to build an exe. If the exe runs, everything that is needed to run is there.

You say there's no error, but do you do any error handling? For instance, are all errors wired, and is there an error handler (or indicator) to notify you of an error? The automatic error handler that you get in development doesn't work in an executable (IIRC).

Very often it's a path (to for instance an image) that is wrong. Relative paths in development don't always work in the executable.

Can you try to compile the simplest example? Just an open, add text, close?

It would help to see what you're doing (and how).

[beuvink]

not using the 'set custom font' by any chance? This caused a problem for me (as I was using it wrong), see earlier in this thread.

Using it in an .exe without any issue or changes to build settings since then.

[Rafals10]

Thank you very much for your help!

The problem is already solved! I have added error handler as Wiebe suggested and recognized that there is a problem with image path. The path was built using application directory contant. So in this case the full path was different when I run the program from the project or from exe. That was the reason I had no error on the project level.

Thank you again! 🙂

Best regards,

Rafał