- Page-open actions. (In Acrobat, Document menu, Set Page Action…
- Links. (Use Link tool, then set Action type in Create Link dialog box.)
- Form fields. (Use Form tool, set up Action.)
Now, in the first three instances here, you’re not necessarily dealing with forms at all.
‘fields object’ methods only account for about half the available properties and methods in
- Programmatically control fullscreen vs. not-fullscreen viewing mode.
- Programmatically control the zoom factor.
- Programmatically control the current page number.
- Programmatically control the current view type.
- Programmatically control the presence/absence of toolbars.
- Make menu commands execute programmatically.
- Issue alert dialogs. And system beeps.
- Issue response dialogs. These are useful for gathering user input without form fields.
- Jump to URLs.
- Send e-mails.
- Go backward and forward on the view stack.
- and more.
Now you might be saying, ‘But in response to what kind of events?’ The answer is, your
scripts can be entered at the time any page is opened or closed, or in response to mouse
clicks. ‘What mouse clicks?’ you may be wondering. Clicks on links, of course! One of the
options you have when setting up Links in Acrobat is to have a click on a link activate a
visible object on the page that you want people to click on), you can consider them custom
buttons, of a sort.
I only bring all this up to remind everyone (myself included) that when we talk about