Mergepdf hime
Acrobat has had its own interface for creating and editing buttons for many versions. I opened up Acrobat to see what was going wrong. The method worked correctly in InDesign CS3 so it could be a subtle InDesign CS4 bug. I did the requisite troubleshooting (like restoring my InDesign preferences) but the problem persisted. As of this writing, I’m not sure what happened (my colleague and friend Sandee Cohen wasn’t able to replicate the problem). When I created a text anchor as I described above and made a PDF, all my buttons worked correctly except that one.
#MERGEPDF HIME HOW TO#
So I’ll use it as an example of how to troubleshoot buttons in Acrobat. In fact, as I was preparing this posting, I ran into one myself. We’d expect that all the buttons we create in InDesign would create perfect buttons in Acrobat.
#MERGEPDF HIME PDF#
When an interactive PDF is created, that should create a named destination that the button will select, jumping to the appropriate page. Make a button, and make its action Go to Text Anchor. By default, it names the text anchor it creates using the text string you selected, although you could rename it.ģ. Choose New Hyperlink Destination from the panel menu. Open the Hyperlinks panel (Window > Interactive > Hyperlinks). (You could make text Paper color to hide it if you don’t want it to be visible.)Ģ. Go to the destination page, and select text in a text frame. (As we’ll see, these have a different name? named destinations?in Acrobat.) Here’s how to do it:ġ. So how do you create one in a PDF file? You need to create a text anchor, and use the Go to Anchor action. Otherwise, you’ll get the message below, and you’ll lose your interactivity:Ĭreating a Go to Page Button in a PDF FileĪs I mentioned in the previous posting, there is a Go to Page action in the Button panel in InDesign CS4, but it’s only for creating buttons to be exported as a SWF file. If you’re using transparency in your document and it in anyway interacts with a button, you must save your file with Acrobat 5 compatibility or higher (no transparency flattening). (Forget trying to create a PDF using Distiller that kills everything.) In the Export PDF dialog, be sure to check Interactive Elements (and also check Hyperlinks if you’re using those in your interactive PDF file).Ĥ. Buttons only “come alive” in an interactive PDF file if you turn on the right options when you export your PDF. Place the picture in a Hidden button, and use the Show/Hide Button action in the Visible button to make the picture visible.)ģ. (Example: If you want a picture to appear when you click a button, create two buttons. Most buttons are Visible in the PDF but each of these options has their uses. You can choose which of these attributes are applied to a button from the Button panel menu. Fields can have four variations of visibility?Visible in the PDF, Visible in PDF but Doesn’t Print, Hidden in PDF, and Hidden in PDF but Printable. In the PDF language, buttons are considered a kind of field (think form fields). Buttons can have different attributes for visibility and printability. This will greatly reduce the number of buttons you need to create, and will ensure consistency.Ģ. When possible, create buttons on master pages in a document. The following list isn’t exhaustive, but, no doubt, those reading it can suggest some other tips:ġ. (By the way, most of these tips also apply to creating buttons in InDesign CS2 and CS3 as well.) This means learning a little about buttons in Acrobat. And there will inevitably be problems along the way, so you need to know something about troubleshooting problems. In this posting, I’ll focus on creating buttons for interactive PDF files in CS4. But there are some critical features which aren’t obvious, especially when you’re new to creating buttons. As I said in my previous posting about creating buttons in InDesign CS4, buttons are now easier to create.