Adobe Acrobat Dc Javascript
End of search results. Display results with all search words. The Acrobat JavaScript model has a global object for holding data that is global to the entire model. Below is a simple example of how it is used. There are two lines of code, each placed in a different location on the same PDF file in order to save and then restore the last page viewed by the user. Adobe® Acrobat® DC SDK JavaScript™ for Acrobat API Reference for Microsoft® Windows® and Mac OS® Edition 1.0, May 2015 If this guide is distributed with software that includes an end user agreement, this guide, as well as the software described i n it, is furnished.
I am unable to get my pdf to work online with Adobe Reader DC.
None of the buttons or functionality is working. (Like when you click motorvehicles, or Mobile homes or any of those buttons across the top a drop down of choices is supposed to appear) But if I open in any other reader it works fine. Does anyone know how I may be able to edit the document to work properly in Adobe Reader DC as well? Is there any settings in the document or anything that you have to change for things to work in DC?
Usb copy protection software. USB Copy Protection 6.10 Perfect solution for publishing on USB flash drives to prevent unauthorized copies, control use rights, set expiration date. Unbreakable copy protection for almost all media files. USB Copy protection Software for PDF, MS Office, HTML,SWF, image, audio, video files, EXE, etc.
I have tried changing the settings in the security section to Acrobat X and later but that did not fix it as well.
radiovisual
1 Answer
Upon Inspection of your PDF document in the Adobe DC JavaScript debugger, I am afraid there are just a whole bunch of syntax errors thrown. When you fix one set of syntax errors, a whole new set of syntax errors pop up. From what I can tell (someone can hopefully confirm this) is that the JavaScript interpreters in the older versions of Adobe are less strict about how they interpret the language, which is why your forms are working in the older versions, but are getting stopped by the latest interpreters in Acrobat DC.
When I inspect the JavaScript that is throwing the errors, I am not only noticing that Adrobat DC really wants you to terminate your JavaScript statements with semicolons, (which your code does some of the time), but I am also finding very strange constructs, some that would leave me to believe that even though your forms are technically not throwing any errors in the older versions of Acrobat, you might find that the forms are not actually behaving properly in the older versions.
So, to fix these errors, and get your forms working in Adobe Acrobat DC, you would have to go clean up all the errors being thrown, which means migrating (updating) your coding style to comply with the new level of strictness in the Acrobat DC's runtime.
For example, when I first open your form using the JavaScript debugger in Acrobat DC, I get the following errors listed:
Notice how you have all these errors like:
These are good indicators that the new JavaScript interpreter in DC is holding JS to a higher standard, and using newer language features, like the classkeyword, and imposing a convention that semicolons must be used to terminate statements.
When you continue clicking around the PDF, the JavaScript debugger starts complaining of even more errors in the same manner (missing semicolons, functions that are not defined, etc), so fixing one issue only reveals another rabbit's hole of additional, yet identical issues.
So I would say the fastest route to getting this form updated and ready for the latest version of DC, is to go through your scripts and apply some conventions or linting to start cleaning up the syntax (terminating all statements with semicolons, etc). Once you have cleaned up the syntax, the JavaScript interpreter is likely to start finding the function declarations that it couldn't find before (due to what it was considering an invalid syntax), which will (hopefully) clear up the 'function not defined' errors.
Also, I would just do some general testing that your forms work the way you intend, because I am seeing strange JavaScript like this sample taken from the CreditCalc function:
Notice that break between lines 123 and 125? That's weird-looking JavaScript to my eyes, and from what I am seeing the code that sits in that 'floating' object on line 125 is not ever going to get hit, it just exists, but won't ever serve a purpose, this should be scary to you.
Strange constructs like that are floating all over your scripts, along with other gotchas that could potentially result in unexpected behaviors, like using != 0 instead of ! 0.
Whitney Houston — ‘Crack is wack!’. Read more quotes from Whitney Houston. Share this quote: Like Quote. Recommend to friends. Friends Who Liked This Quote. To see what your friends thought of this quote, please sign up! 7 likes All Members Who Liked This Quote. Whitney houston.
So I'm afraid there is no easy answer here, you will likely have to do a lot of cleanup before Acrobat DC lets you run this form.
radiovisualradiovisual