|Language:||English, Spanish, French|
|ePub File Size:||16.60 MB|
|PDF File Size:||12.62 MB|
|Distribution:||Free* [*Regsitration Required]|
To enable text selection, some extra steps need to be followed. Instead of writing callbacks such as success or error here and there in your code, you just chain the various callbacks involved by a then for success or catch for error. Normally, we're not interested in these initial messages. JS has been used. However, these are still the settings used by the Console Window.
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.
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.
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.
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.
We've just found out something that would have taken us just a little more effort to find out using the Acrobat property dialogs, and the information is in a very usable format. We can easily copy and paste this information to accomplish some other purpose, for example applying the color to another field with this line of code:. Suppose a document needs to be checked for branding purposes, i. The following code uses a simple loop to display this color info in the Console Window for manual inspection:.
Because of the loop, this code cannot be executed one line at a time. It has to be done all at once. Notice that in the loop there is a function called console. It's in the fourth line. This function writes text to the Console Window and it will be discussed in the next section. Here's an example of a function that does not have an easy equivalent on the regular Acrobat menus and toolbars.
Enter the following line into the Console Window and run it:. Acrobat will create a new, blank PDF document. This is perfect for trying out new ideas before applying them to a working document.
The results of this operation are shown in Figure 7 below. Note that yet again, the result is something different. The result shown in Figure 7 tells us the type of object created. This result is only useful in letting us know the function worked. If app. Both of these situations would have been displayed in the Console Window.
The path property is exactly what you might think it should be. It's the folder path of the current document. Since the current document was just created with app. The result will look something like this:. Of course, this information is easily available in the Document Properties dialog.
The advantage to using the Console Window is to make this information available to copy to the system clipboard for use with another script in Acrobat or for something else.
The reference contains examples for all properties, methods and events, and is continuously updated according to the latest web standards.
We recommend reading this tutorial, in the sequence listed in the left menu.