I prefer the options as they are shown in Figure 1, but uncheck this option before exiting the preferences. The reason for not enabling the debugger is because it has a significant negative impact on Acrobat performance, and can even cause Acrobat to crash.
So the only reason you would actually turn on the debugger is if you needed to use the debugging tools. If you don't already know how to use software debugging tools, you are much better off sticking to the Console Window. A very useful feature is the external JavaScript editor, since the default Acrobat editor is very basic.
A good JavaScript editor will have advanced features that make code manipulation and navigation easier when you are editing document code. You won't be using the JavaScript editor with the Console Window, but this group of settings has an interesting effect on it.
The Acrobat editor font and size settings are the same settings used in the Console Window. You can see in Figure 1 that I have chosen to use an external editor. This selection disables the Acrobat editor and grays out the font and size settings. However, these are still the settings used by the Console Window.
If you want to change them you'll need to temporarily enable the Acrobat editor to modify the settings, then reselect the external editor. In order for the settings to take affect you'll need to close and reopen the Console Window. After these preferences have been set Figure 1 , you're ready to start using the Console Window.
The shortcut key can be a bit tricky on the Macintosh because there are slight differences between the keyboards on laptop and desktop systems. So the keyboard shortcut is not always valid, but the tool button will always work. The tool panels are a new feature introduced in Acrobat X, so displaying the Console in earlier versions is slightly different.
The Shortcut key is the same, but instead of a tool button, these earlier versions use a menu item. The Console Window section of the Debugger is in the bottom portion of the dialog, in the area labeled View.
In Figure 3, the View pull-down selection list is set to Console, meaning the Console Window is being shown. This area is also used to show the Script window for displaying runtime code when the debugger tools are enabled. In the figure, the Console is being shown immediately after Acrobat was started. The status messages are displayed by code built-into Acrobat and loaded on startup. Each line represents a JavaScript module loaded by Acrobat.
If there were any problems with these modules, or any others that Acrobat loads, error messages would also be displayed here. Normally, we're not interested in these initial messages. So if you would like to try out some of the code presented here as examples, then clear the window by pressing the button that looks like a garbage can in the lower right corner of the window.
Now we have a clean work area and are set up and ready to start using the Console Window. JavaScript code can be executed directly from the Console Window. This ability is a huge time saver since it provides a fast and easy way to test out code before it's placed into a scripting location where it will be more difficult to debug.
To run the code, make sure the cursor is on the same line as the text. You can place it anywhere on the line as long as nothing is selected. Either of the two following actions will cause Acrobat to run the code. Acrobat always attempts to convert the result of an execution into text so that it can be displayed.
Sometimes the result of an operation is not as clean or obvious as a number. Let's try something that doesn't have such a well-defined result. Enter the following line in the Console Window and run it:. This calculation has an obvious mathematical error, but Acrobat JavaScript doesn't display an error message.
Instead, as shown in Figure 5 , it displays the word "Infinity. It is much easier to find this kind of issue by executing individual lines in the Console Window where you can see the results immediately, than it is to debug it from a field-calculation script. The next line of example code is something that might be used in a real script.
It assigns a simple addition to a variable named 'sum'. As shown in Figure 6, the return value from this line of code is "undefined. The calculation is executed and applied to the declared variable, sum. However, the first and primary operation on the line is the variable declaration, so this is the operation that returns a value to the Console Window.
Unfortunately, variable declarations do not return a value. To overcome this small issue, the Console widow displays "undefined. Anything that doesn't exist to the JavaScript environment is "undefined. This action executes just the selected text. This technique of selecting parts of the code for execution is also useful for executing multiple lines of code. So far we've talked about executing code in the Console Window for testing and debugging, but there is no reason to restrict our usage to this limited theme.
Immediate Mode means that anything entered into this window is executed directly by the JavaScript engine. We can use it anytime we want to execute code for any purpose. Two uses for the Console Window besides code testing that immediately come to mind are automation and analysis. There are several functions in Acrobat for manipulating and for acquiring information from PDFs and Acrobat. For operations with a user interface button or menu item, the main advantage of using JavaScript is greater flexibility, since JavaScript functions typically provide more options than the user interface equivalent.
For example, suppose you wanted to know the exact border color of a text field so you could use the same color in another location. Assuming the current document has a field with the correct name on it, the following code displays the raw color value in the Console Window:.
The result of this operation is a color array. Remember, Acrobat attempts to convert all results into text. Arrays are converted to text by converting each individual array element into a text string, so the result would look something like the following line when it is displayed in the Console Window.
JavaScript Editor. You can use the JavaScript Editor to create and edit scripts. Document actions and JavaScript. Select an action and then click Edit to add the script to the action. Sign in to your account. Sign in.
Connect and share knowledge within a single location that is structured and easy to search. I have a simple pdf file containing an embedded file test. I've read that to perform that, the JS that should be used is this:. For some reason, it is not working.
I checked the debug js console on my Acrobat reader DC version ExportDataObject is not a function. I'm not sure why on my "this" object the ExportDataObject is not available I think it should be available always, shouldn't it? I also tested without the this. That makes to think to me that this. ExportDataObject is existing but is not a function as the original error said Not sure how to make this work. Not sure if next steps should more JS debugging or if the problem is related to something on pdfs or Acrobat.
Any help? Javascript function names are case-sensitive and as documented by Adobe p.
DEFAULT
DEFAULT
Adobe acrobat pro dc javascript debugger free -
In this tutorial, learn how to code Acrobat JavaScript, including testing and debugging code with the Acrobat JavaScript Console window. [PDF] Acrobat JavaScript Scripting Guide - Adobe. You can use the Dbgobject, available only in Acrobat Pro, to optionally control the JavaScript debugger.
DEFAULT
DEFAULT
Reader And The Javascript Console - JavaScript Editor
Create digital signatures. So the only reason you would actually turn on the debugger is if you needed to use the debugging tools.
DEFAULT
DEFAULT
DEFAULT
DEFAULT
0 comment