Quote from Ronnie on June 2, 2019, 4:02 pmHi, not sure if anyone experienced the same symptom. When I compiled the neoPDF-Tutorial to Windows EXE, the PDF was not shown. It works fine in browser or generated HTML, but not in EXE. Anyone can reproduce the symptom? Thanks
Hi, not sure if anyone experienced the same symptom. When I compiled the neoPDF-Tutorial to Windows EXE, the PDF was not shown. It works fine in browser or generated HTML, but not in EXE. Anyone can reproduce the symptom? Thanks
Quote from matty47 on June 3, 2019, 12:00 amHi, I tried the example and found it did not render the pdf in the built in debugger/preview. Error was 'Promise' not defined.
Tried the generated webpage in IE11 and received the same error. 'Promise' not defined line 118 in jspdf.min.js
Windows exe did not render the pdf.
Opera and Chrome web browsers opened the generated web page and displayed the pdf OK albeit slowly.
When I tried an internet webpage with an example of jspdf it failed to run in IE11.
Windows 7 home.
Hi, I tried the example and found it did not render the pdf in the built in debugger/preview. Error was 'Promise' not defined.
Tried the generated webpage in IE11 and received the same error. 'Promise' not defined line 118 in jspdf.min.js
Windows exe did not render the pdf.
Opera and Chrome web browsers opened the generated web page and displayed the pdf OK albeit slowly.
When I tried an internet webpage with an example of jspdf it failed to run in IE11.
Windows 7 home.
Quote from luishp on June 3, 2019, 11:00 amHi @ronnie and @matty47,
Compiled EXE apps use IE as the rendering engine.
Although Internet Explorer will not render inline PDF it's possible to download the generated document.
Just add some additional JavaScript libraries in order to fix the "promises" error in neoPDF plugin.
Go to Project > Properties > Advanced > Custom metadata > Head and add this code:<script src="https://cdn.jsdelivr.net/npm/es6-promise@4/dist/es6-promise.min.js"></script> <script src="https://cdn.jsdelivr.net/npm/es6-promise@4/dist/es6-promise.auto.min.js"></script>Or download the JavaScript files from the CDN and add them to Project > Properties > Libraries/Files
Then just replace any neoPdfRender with neoPdfDownload.Regards.
Compiled EXE apps use IE as the rendering engine.
Although Internet Explorer will not render inline PDF it's possible to download the generated document.
Just add some additional JavaScript libraries in order to fix the "promises" error in neoPDF plugin.
Go to Project > Properties > Advanced > Custom metadata > Head and add this code:
<script src="https://cdn.jsdelivr.net/npm/es6-promise@4/dist/es6-promise.min.js"></script> <script src="https://cdn.jsdelivr.net/npm/es6-promise@4/dist/es6-promise.auto.min.js"></script>
Or download the JavaScript files from the CDN and add them to Project > Properties > Libraries/Files
Then just replace any neoPdfRender with neoPdfDownload.
Regards.
Quote from Ronnie on June 3, 2019, 3:41 pmHi @luishp
Yes, I've tried as suggested, using both options (script src, and Libraries/Files) as suggested. It works. However, as you mentioned, the constraint is it doesn't work inline... hence the pop-up download dialog and separate browser window opening the PDF file.
Just a suggestion... perhaps to enhance the neoPDFDownload function to include additional 2 params like
neopdfdownload "[pdftext]" "[downloadfile]" '[ReturnStatus]"
where [downloadfile] is the path/filename of the download file location, and [ReturnStatus] is the return value (like 0,1) to denote file has been downloaded successfully or not completed yet which is useful for huge pdf file size. This way, there is no filesave dialog popping up...
Hi @luishp
Yes, I've tried as suggested, using both options (script src, and Libraries/Files) as suggested. It works. However, as you mentioned, the constraint is it doesn't work inline... hence the pop-up download dialog and separate browser window opening the PDF file.
Just a suggestion... perhaps to enhance the neoPDFDownload function to include additional 2 params like
neopdfdownload "[pdftext]" "[downloadfile]" '[ReturnStatus]"
where [downloadfile] is the path/filename of the download file location, and [ReturnStatus] is the return value (like 0,1) to denote file has been downloaded successfully or not completed yet which is useful for huge pdf file size. This way, there is no filesave dialog popping up...
Quote from luishp on June 3, 2019, 11:08 pm@ronnie, as far as I know there is no possiblity to save any file on the user device without a confirmation dialog. This is due to security reasons. The browsers usually save files on the "download" folder. Not sure if it's possible to know if the file has been downloaded sucessfully or not. Will investigate it.
Regards.
@ronnie, as far as I know there is no possiblity to save any file on the user device without a confirmation dialog. This is due to security reasons. The browsers usually save files on the "download" folder. Not sure if it's possible to know if the file has been downloaded sucessfully or not. Will investigate it.
Regards.