Navigation Button Tricks for Interactive PDF on an iPad
When I’ve been working on creating interactive PDFs that will be viewed on an iPad, I’ve been frustrated by the immature applications available for reading and working with PDFs. I’ve written about this in the past year before here and here.
One of the most maddening problems was just getting simple navigation buttons (Next Page, Previous Page, etc.) to work properly. If you create navigation buttons in InDesign CS6, they work fine in Acrobat Pro or Reader for Macintosh or Windows, but they do nothing when you click on them in Adobe Reader on the iPad. Another problem is that, even with PDF Expert, a paid PDF reader app I recommended in the postings above, the buttons work, but the text for the buttons doesn’t display properly.
Creating Navigation Buttons in Acrobat
An Acrobat expert, George Johnson, explained the problem with navigation buttons creating in InDesign CS6 not working in Adobe Reader, in a posting on the Adobe Reader for iOS forum:
The problem with InDesign is in using the Go To Next/Previous Page options in InDesign, it creates an Execute a Menu Item action when exported to PDF, and since Reader for iOS doesn’t have menu items or interprets such actions otherwise, they are just ignored.
When I first created some navigation buttons in InDesign CS6 like those shown below, the Go to Destination action and Go to URL actions worked in Adobe Reader for the iPad, but the First Page, Previous Page, Next Page, Last Page buttons did not.
If you examine the buttons that don’t work in the Forms Editing feature of Acrobat Pro, like the Next Page button shown below, the PDF sees the navigation command as a menu command. This is a menu which appears in Adobe Reader and Acrobat for the Macintosh and Windows, but not on an iPad.
The workaround is to create those buttons in Acrobat. This requires a different workflow. Here’s what I did that works in Adobe Reader:
1. Instead of placing the navigation buttons on a master page, I created the four buttons (First Page, Previous Page, Next Page, Last Page) only once, and I placed them at the bottom of page 1. I didn’t give the buttons an action. (The other buttons can be created with actions in InDesign.)
2. I exported to PDF (Interactive) and opened it in Acrobat Pro. In Acrobat Pro XI, I chose Tools > Forms > Edit. In the Forms Editor, I right-clicked each of the four buttons on page 1 of the PDF, to bring up a contextual menu and chose Duplicate Field, and chose to duplicate the buttons on each page of the PDF.
3. Then for each button, I created an action in Acrobat Pro which created the navigation to the desired page. I double-clicked on each button. On the Actions tab of the Button Properties dialog, I selected a Go to a Page View action.
4. After choosing the action, I was prompted to navigate to the destination page as shown below.
5. The resulting PDF, when transferred to Adobe Reader on the iPad, worked perfectly.
Be aware that Adobe Reader still does not support Show/Hide buttons, nor does it support video or audio files.
Another Workaround for PDF Expert
Readdle’s PDF Expert, which I’ve written about before, has a different kind of limitation with buttons created in InDesign CS6. It has apparently created its own workaround for the navigation buttons which doesn’t require using Acrobat Pro. While the buttons work to navigate, you can’t read the text labels on the buttons! For PDF Expert, the workaround is to outline the type which is contained in the button. The screen capture above was created in PDF Expert after using that workaround.