Adobe Acrobat X: Buttons - Part 1

A lack of PDF buttons

There is scarcely any aspect of Adobe Acrobat dealt with leaner than the idea of using buttons in a PDF document. If you do a web search for this topic, you will find very few articles, and most of them involve using JavaScript with the button actions, or they actually use LiveCycle Designer, which I don't get to use, because I am on a Macintosh. (Hey, LiveCycle Designer programmers, why don't you port that over to the Mac?)

So, I of course, aim to remedy this lack of information on Acrobat buttons and all the wonderful things you can accomplish with them.

For now it should be enough just to create a button and show how to get it to do something. Later we will try more and advanced stuff.

What you can do is follow along, if you download the sample working file(s) I have made available here. Otherwise, you are invited to create your own project as we go along.

Simple Button Creation

I will open a simple document of a few pages, with an indicator of the page number on each page. Nothing fancy.

Another thing; I am using Adobe Acrobat Pro XI, so the placement of tools and items within your version of Adobe Acrobat may be different.

So, first step: find and choose the button tool. In Adobe Acrobat Pro XI it is found in the Interactive Objects tools pane. If you don’t see Interactive Objects, then go to the menu View > Tools > Interactive Objects. (Previous versions of Adobe Acrobat Pro may have the Button tool in the Content toolbox or elsewhere.)



Next, draw out a box about 1 inch wide and 1/2 inch high with the Button tool. You notice a pop up will show immediately with a field name of “Button1” and little else, except one text line in the bottom right corner saying “All Properties.” For now don’t click that.

Of course, you’ll notice that the button is a field, for it says Field Name. Buttons are part of the whole form fields package that Adobe Acrobat Pro makes available. Because of this, a button has many uses  you may not even imagine yet. However, there are a couple of particulars you need to keep in mind because of this.

Number 1: as a field, each button should have a unique name given it. If any number of fields in a PDF file have the same name, the function of the PDF may get messed up, since the same data or function acted upon one field with that name, will be attached to the other fields with that name. The only exception would be the Radio Button form field, which we cannot spend time on right now.

A button field, though it doesn’t act like any other part of a form, will be recognized as a form element, and so the PDF file with only one button will be recognized as a form and may open with a menu bar for working with forms.

OK, back to our button. Now it’s time to click the All Properties link at the bottom of the big label box. This will open the Properties dialog. (If you have already clicked anywhere else in your document, you may have noticed the label box went away. That’s OK, you can get to the All Properties dialog by double-clicking on the button.)

You see that the name of the button is selected here. Let’s rename it to say “Page2.” Hit your Tab key to move into the Tooltip field and type in “Goes to page 2.” The Tooltip gives the user a clue what the button (or any field) is for by showing your tip as the cursor hovers over the button. The Tooltip also acts as Alt Text for interactivity and compliance.

Next, select the Appearance tab to see the options there. You notice the fill color is currently a light gray (the default). Click on the little gray swatch next to the Fill Color label and choose something like a pure magenta. Depending on your operating system, you may have differing available color pickers.

The Text section sets your style of text in the label of the button, which is the text that shows up inside your button; this is only an option of course, you don’t have to have any text if you wish to keep your users guessing, or if prefer to use a graphic for your button otherwise (more on that some future time).

One quick note about the Font you choose. You will see a few fonts in the very top of your font list, with a line dividing these from your usual fonts list. These are the lowest common denominator fonts, meaning that everyone who opens your PDF file should have those fonts. It is best not to use fonts from below that line UNLESS you can guarantee every user of your PDF file will have those fonts available on their operating system.

Now choose the Options tab and observe the many possible settings you have available. For now just place your cursor in the Label area and type “To page 2.” When you hit the Tab key you should see your text appear in the button.

Now we have a button that is presentable to the user, except for one thing; we have to make the button do something! So, choose the Actions tab next. You may observe the straightforward options presented here. You have a Trigger to choose, and the drop-down list is filled with six possibilities. We will get to explain these in further excursions into Acrobat buttons, but for now, just leave it at Mouse Up.

Suffice it to say that the Mouse Up option is the default behavior for just about any button in a computer application or web page. The action is triggered when you release the mouse button from the button, rather than on the click down. This allows a user the option to think twice about triggering the action, and to move the cursor away from the button before releasing it to avoid the action.

So, now we get to say what we want to have happen. Drop down the menu for Select Action to see all the possible types of actions available. There are quite a number of choices, but for now scroll down a few to, “Go to a page view,” then click on Add....

You will see a little window come up with the instructions for creating a link. Navigate to page 2 of this PDF file and then click on “Set Link.”

Now you may close the Properties box and select the hand tool. Click on your new button and watch it move to page 2 of the PDF file.

Congratulations! You now have a fully functioning button!

Adobe Acrobat Learning

If you have been around in the graphics world for a little while, I would be surprised if you have not heard about Adobe Acrobat and how it is used for PDF file creation and editing. Adobe has certainly had great success with this file format, and Acrobat is undoubtedly the most capable of PDF file editing and optimizing applications available.

True, there are many other PDF-editing applications, some smaller in scope, and others that way out-perform Acrobat. However, Acrobat is what I use in and outside of work. I have used Acrobat since it was first released in 1993, and I have never encountered another file format or application that comes close to it's usefulness for sending files to others for work evaluation or information sharing.

By the way, what was that file format that Microsoft was going to launch as its own kind of “portable document” file? Did it fall flat on its face?

When Acrobat first came out, there was one other file format some company had begun to bring out. I remember it was called Common Ground, and it may have first started on the Unix platform, on Sun workstations. However, it never amounted to anything. Acrobat came on the scene and dominated almost immediately. The only problem with it at first was that QuarkXPress stubbornly refused to support the PDF file format. That later proved to be a contributing factor to QuarkXPress’ downfall from its lofty perch.

Anyway, I think it is high time I should concentrate on sharing some of the most important things I have learned while using Adobe Acrobat over the years. Over the next few weeks or months I will share out of my “vast depth” of experience, and hopefully some of these pointers will be useful to you.

Photoshop: Lighting Effects Returns!

Ye Olde Lighting Effects

On my latest excursion into the recently released Adobe Photoshop CS6 I stumbled upon a great surprise: Adobe has brought back and revamped the stalwart filter Lighting Effects.

If you are familiar with the latest releases of Adobe's Creative Suite, you probably were made aware of some of the features of Photoshop dropping out of existence because of the move from 32-bit to 64-bit processors. Between CS4 and CS6, Lighting Effects was one of them, along with others like the Extract command. The Extract command has returned within the confines of the Refine Edges panel, but nothing replaced Lighting Effects. Unfortunately it was just gone, much to my discouragement, because I have relied on that feature for many things.

Revamp a plain background with Lighting Effects

Happily, Adobe has updated it for 64-bit processing, and made it better by a few degrees as well. For your learning insight, I will go through an example of using this handy feature. I will start with a basic setup for a logo, with somewhat of a glow, neon effect. To give it more atmosphere I aim to embellish the "wall" this neon logotype hangs on.



Currently, the wall is plain and lifeless. It certainly doesn't give us the idea of someone turning the lights on after normal operating hours. So, I will add a couple of lights. After copying the blue background layer, I opened the Lighting Effects filter by going to Filters > Render > Lighting Effects.

A new interface for filters

The first thing I noticed when I opened this filter is Photoshop CS6's new interface for filters and similar operations. Photoshop keeps as many aspects of this filter interactive on-screen, with the panel controls off to the side. Certain controls are available by clicking on certain areas of the on-screen light proxy. As far as that goes, you don't even notice any difference between normal editing mode and this one, except for the fact that you have to hit an apply button to get out of this filter operation.



To rotate the light, place your cursor over one of the handles of the outer ellipse. To expand or contract the light's illuminating area, click on the inner ellipse. Change the intensity of the light source by dragging within the inside central ring. You choose which type of light you currently are using by the top menu on the options panel. Additional lights are available at the upper left of the window.

After setting the first light, I added another spot with a slightly greener blue color.



Use a texture with Lighting Effects

Now, this basic lighting effects stuff gives us a good start. However the wall is still just flat and uninteresting. I am thinking this would look much more appropriate as a brick wall. So, I just so happened to have created a seamless brick pattern to use. How will I use this? As an alpha channel that we can plug into the lighting effects Texture option.

So, I next create an empty layer with the brick pattern overlay fill. The best approach for seamless patterns is to create them amply large, so you only need to scale down rather than up for their use. Here, I scaled my pattern down to 19 percent. (Hint: A pattern overlay allows you to scale it!)


So, then I viewed this layer alone, opened the Channels panel, and copied one of the component channels (the Blue one) to make a new alpha channel. Next, I inverted this alpha channel, and brought in a Texturizer filter, to give the bricks some roughness.




Load edited alpha channel into LE Texture option

Now I'm ready for the final touch. I open the lighting effects filter settings on the wall layer and go to the Texture option. Then I choose the alpha channel I just finished editing to allow lighting effects to use it for a bump map.

Now we can see the final result is much improved from the plain original, thanks to what lighting effects can do.

Ernie's blog: On A Quest To Hire The Über Production Artist

Ernie adds to the Production Artist dialog with a thorough article.

Ernie's blog: On A Quest To Hire The Über Production Artist

Video Compatibility Across Platforms

Like many other production artists, I work on Macs. Most office-related employees, such as account managers, work on Windows-running PCs. When is comes to exchanging documents between these platforms (and Unix computers), many things have become much easier than it was about six or more years ago. For example, fonts have turned a major corner over the last few years with the entrance of OpenType formatted fonts (.otf). The same OpenType font can function the same on any platform you use your document.

One Arena Remaining

Alas, the same is not true for video files however. For the most part, the video world is a morass of choices to make, like going into an ice cream shop with hundreds of flavors. I'm not talking about the web, of course. Most web videos, such as go on YouTube or into a web movie preview site, are translated via a Flash player or some QuickTime format. But when you want to have a video file say, saved from iMovie, play on a Windows PC in a specific program, like PowerPoint, then you may run into unscalable walls.

I have worked at previous companies that had some video production software and hardware that helped out in this regard. I’ve worked with Final Cut Express and related programs. With those, the translation to other video formats is a lot easier. But where I am working now, there is not much to work with except iMovie, QuickTime, Flash, iMovie HD and Adobe Media Encoder.

There are a number of video file formats available that most people are familiar with, but also dozens more. There’s QuickTime (.mov), Windows Media (.wmv), Audio Video Interleave (.avi), MPEG, or Moving Picture Experts Group (.mpg), DivX-Encoded Movie File (.divx), and so forth. For a comprehensive list this FileInfo page is good.

File formats for video, however, are only containers for the content. What’s more important are the languages used to translate that content from the file to the player. These are called codecs. Codec stands for COMpression and DECompression language. A video file natively is really big. Think of hundreds of pictures put together in a sequence, with each picture a certain resolution and dimension. Just one frame from an HD 720p video frame is 2.64 megabytes. Just a short minute of video that size could be almost two or more gigabytes!

So understandably to store and transfer video, we need these codecs to shrink the size of the video files. And when we play it, we need this codec to decompress it on the fly and send each frame to the player in time. Some codecs do this efficiently and some not so much. And the older the codec, the probability is that it degrades the original video a lot, or doesn’t compress it very much.

All this is enough to understand why I had the worst time trying to get a video file saved out of iMovie to play in Microsoft PowerPoint 2007 on a Windows PC. It would seem that there are many codecs for Windows Media files (.wmv) that are not accepted by PowerPoint. Now I am pretty sure that MS PowerPoint must use the system media capabilities rather than its own. I figured we needed a conversion capability to go into a Windows Media format. At the time, I only knew about Flip4Mac, which can play WMV files. A paid upgrade will allow some saving into WMV format. I soon would find out that it must take a lot more than just any WMV file to play on PowerPoint.

Flip Over This

My first impasse was with Flip4Mac. I got approval to spend the $39 to upgrade to the first level of capability for Flip4Mac to save out to WMV format on a Mac. I found quickly that $39 (plus tax) is not enough. For that price, you get a maximum of 640 pixels wide and only one pass VBR (Variable Bit Rate encoding). And the resulting quality is horrible. Not only that, but it isn’t available out of iMovie ’09. In fact, it isn’t available through QuickTime directly unless you wish to spend another $30 for QuickTime Pro. I only found the capability via iMovie HD’s Share menu. (To upgrade fully to all the WMV options you could need, please pay an additional $130 to the makers of Flip4Mac.)

What was even more disheartening was that the resultant WMV file would not play in MS PowerPoint on the PC. It played in Windows Media Player, however. Now if it is made by Microsoft, and it plays in one application they make, but not in this other one, what is the problem? Why wouldn’t Microsoft make all their applications compatible with what they work with, across the same platform, which they are owners of as well? Further trials to AVI and other formats did not help either.

Some Other Options

In the process, I found a couple of web sites that offer conversion of video and audio files to various formats. They are in beta version, and offer their services free to start. If you wish to have storage space or other features, you need to pay monthly fees that vary with the options available. One site is called Zamzar, which I liked because the quality of their conversion is very good. However, they use a DIVx codec, so video from there did not play in PowerPoint on a PC for me.

I tried getting QuickTime installed a PC to test whether QuickTime movies would play in PowerPoint on the PC. Nope. (Is there some issue with a PC and video of which I may be unaware? Possibly.) All I got was a black box where the video should have been on the slide.

The Answer

Well, after a few more well-considered options, and finding no solution, I decided to go a route I was pretty sure would work. Each of the PCs that were going to run this presentation had an up-to-date installation of Adobe Reader, version 8, 9 or X. And that meant one thing for video: Flash Video, or .flv format.

Over the last few years Adobe has been working on the problem of video compatibility. Since there seemed to be no progress between Windows Media on the PC and QuickTime on the Macintosh, the programmers at Adobe went ahead and made their own media format to run cross-platform without depending on the operating system’s video rendering engine. They came up with Flash Video format. This works now inside Adobe Acrobat, Flash and other Adobe programs.

So, to make this easy to end, I converted the QuickTimes from iMovie to FLV via Adobe Media Encoder. Then I saved out the PowerPoint presentation as a PDF, sans the videos. Then in Acrobat I placed the videos, set up the transitions to auto flip based on the rehearsed times from the PowerPoint presentation. And now everything in this project functions just fine on PC and on Mac. And that’s all I was asking for.

Microsoft Office and the Graphics Blues

There is a persistent mythology in the office/corporate world that the suite of Microsoft Office applications, MS Word and PowerPoint in particular, are useful and capable for creating print-ready materials, that is, printed professionally at a print shop. Along with that follows the corollary that web graphics are just as good for print, and thus many logos are grabbed from web pages and given to some designer or marketing department to use for brochures and other printed materials.

Now both of these are as far from the truth of good graphic art as you can get, and each for its particular reasons. The Microsoft Office applications are what is of particular interest to me here.

Now, to be fair, some of the reasons for this are not completely the fault of the programmers’ lack of vision or ambition. The aim and purpose for these apps does not include print-ready work, such as annual reports and brochures. They were intended to be used for work that will be printed on the office copier/printer.

In return, Microsoft never has placed any kind of disclaimer on their packaging or installer that squawks to the user, “Don’t use these for anything you need to print professionally!” And so there is still much ignorance in circulation over the Office Suite. For that matter, any office productivity application is the same, including Open Office, iWork, and so forth. And with the introduction of MS Word’s Publishing View, people are even more apt to be mislead.

Do you realize there are still (and probably still will be) many MS Office files getting submitted to print shops? In fact, many probably are being submitted to print shops as PDF files saved out from Office documents, which in some cases leaves the print shop employees rather stuck with how to properly service them. But that is a topic for some future article.

But let’s tackle one small issue first, and that is what kind of graphics should be placed in an Office document in order to get a decent output from an office printer? When it comes to presentations made solely for on-screen viewing or projection, and mostly from PowerPoint or some like application, it really is of no consequence what the overall quality of an image is. As long as it looks good on screen, it will display or project just fine.

There are many file formats you could choose, but the best are PNG, JPEG, EPS or PDF. I like the PDF option the most, because it can accommodate vector elements as well as raster or photo elements. Also in my most recent tests I have found that the latest versions (2010/2011) of Microsoft Office handle EPS files very well, even rendering them on screen in PowerPoint presentations with surprising quality. (Some of you may remember that EPS files used to only display their lo-res preview in older versions of PowerPoint.)

Printing is another issue altogether, of course. To get this right (for those of you who may not know) we have to look at something called resolution. Resolution has to do with pixels, which is what any kind of digital photograph, for example, is made of. The resolution is usually measured in either of two ways. One is the total number of pixels in an image. For example, a photo at 8 megapixels is basically 8 x 1024 or more than 8,000 pixels across. Otherwise, look at the published dimensions of the file, and note how many pixels in an inch (or whatever unit of measure you use). For example, if our 8 megapixel image were printing at 10 inches across, then it would be roughly 800 pixels per inch across. That’s what we would call a high resolution image.

For screen display or projection of MS PowerPoint images, they need only be at the most 100 pixels per inch, and can easily get by with less. For print, it has generally been the rule to have an effective resolution of 300 pixels per inch, or 300 ppi, all for reasons we don’t have the time or patience to explain here. Let’s just say that it’s regarded as enough density to keep from seeing individual pixels on the page.

Also remember to keep the scale of your graphic to maintain the resolution of 300 ppi. What throws that out is enlarging your graphic. Generally you can scale down, but not up. Scaling up will reduce the overall resolution. If my graphic came in at 2 inches wide and 300 ppi, then I scaled it to 4 inches, it would be only 150 ppi, because at twice the size, it will be half the original resolution. We effectively spread those pixels out over a greater dimension.

When you initially import a graphic into an Office document, it will come in at the original size and resolution at which it was created. That is helpful, because in earlier versions, it might come in at an unpredictable size. On the other hand, it can be hurtful if you are importing that 8 megapixel photo.

Now let’s discuss the fun topic of color. If you’re not familiar with the subject, there are two basic color models we work with in the document publishing world: RGB and CMYK. RGB stands for Red, Green and Blue, which are the main colors that separate from white light. This is what all electronic displays use, from TVs to your iPod screen. On paper, we have to place pigments mixed together to render all the possible colors. We can’t afford to print lots of colors, so a process was invented to mimic the opposite of what RGB does. Making that long story short, we use Cyan (opposite of Red), Magenta (opposite of Green) and Yellow (opposite of Blue). And we add in Black (K) to give us a real black, because the other pigments are not perfect.

With all that said, Microsoft Office and all other office applications use the RGB color model. Professional printing uses CMYK. So that makes MS Office documents incompatible with the printing process, initially. The fact is, however, there is less need for CMYK original documents. There is more than enough technology that is able to convert RGB documents to the needed CMYK for the printing press. The only caveat about it is that if you leave your document RGB and have your print provider convert the colors to CMYK, then you have no real control or say in what the end result will be, because colors will shift, especially if you picked out bright colors.

One solution would be to pick colors, not from the default Office applications’ set, but from the computer’s color mixer app via the More Colors... option. In there, choose the CMYK sliders to make your colors (sorry Windows users, this is only on the Mac OS!). Sure, the color model is still RGB, but at least your color choice will fit the range of colors CMYK can reproduce on a press.

If you do have to send a Microsoft Office document to a print shop, don’t. The best strategy is to save it out as a PDF file. This will prevent the printer from not getting the proper fonts and graphics that you used in your documents. However, if changes need to be made, you will need to make them and send the print shop a new PDF file. New versions of MS Office have the PDF format as an option in the Save As dialog, and believe me, it makes a better initial quality of a PDF file than using such things as PDFMaker.

In conclusion then, you have challenges and choices in how you use Microsoft Office applications, what you place in them and for what you use them. Keep the ideas I discussed here in mind, and you will have better quality results.

A Circular Ending

Sometimes you find yourself needing a quick way to accomplish tasks and assume that those methods somehow work the same across applications. I recently ran into a big issue over a small detail that tripped up the quality of my work, and that of others. I needed to turn a rectangle into a capsule or end cap, for lack of a better description. Not an oval, or just a roundly-cornered rectangle, but a shape that ends in a perfect half-circle. Where I currently work, this shape is an essential part of our brand identity.

There is a certain method you can use in QuarkXPress, Adobe InDesign and Adobe Illustrator, combining a circle precisely placed halfway over the end of a rectangle using a Unite or Merge path function, also called Pathfinder in Adobe Land. (Some future time, I should explain and demonstrate Pathfinder more thoroughly. It’s the best graphic invention since sliced bread.) If you had the circle placed exactly halfway, you should get a perfectly circular end for the shape, with no doubled anchor points where the rectangle’s end and the half point of the circle overlapped. A look at the anchor points of one example created in Adobe Illustrator shows a proper result with just three anchor points.

However, I am one to try doing this stunt in less time and with less clicks. That’s my motto! I can create this using just one rectangle.

Here’s how it works in QuarkXPress: Copy the short width of the rectangle, paste it into the corner radius field on the Measurements palette and divide it in half. For example, if a rectangle had a short side of just 6 picas you would enter “6p0/2” into the corner radius field. (This allows you to use a rectangle of any measure; you don’t have to do the math.) Unfortunately, in QuarkXPress, you need to use a short size no more than 4 inches; QuarkXPress’ corner radius is STILL limited to 2 inches.
Anyway, I digress. What is your result? A perfectly circular end cap.

“Now,” I”ll say to myself, “I should be able to do the same thing in other applications. No problem.”
So, I’ll go into Adobe Illustrator. Here’s a slight difference, because Illustrator’s corner radius is not dynamically adjustable. You have to know ahead of time what the radius should be, and that totally depends on you knowing what the short measure of the rectangle will be when you draw it out. Have fun there. But if you have a dimension in mind, you can Option-click with the rounded rectangle tool, and right there enter the half of the short side’s measure for the corner radius (as shown).

Luckily, Adobe Illustrator also has a cool feature in the Effects menu for a square cornered rectangle you already have drawn out. (And it also works on open shapes too, so it’s handy for die lines and such things.) Select the rectangle, copy the short side’s measure from the Options bar, and go to Effects > Illustrator Effects > Stylize > Round Corners. Paste the measure into the radius field, then type “/2” after it. If needed you can expand the appearance of your end cap, but of course it’s not necessary.

What’s next? Adobe InDesign. And here’s where the trouble comes. I expected all these years that Adobe InDesign would act the same way as QuarkXPress and Illustrator. But I recently discovered that NOT to be true.

In previous versions of InDesign, you can use the Corner Options dialog to set it, similar to Adobe Illustrator. Curious and disappointing is the result you get if you want the perfectly circular end and input half of the short side. Compared to a true circle, you will notice the bulge. It doesn’t even pretend to be circular.

InDesign CS5 now has the ability to dynamically change the corner radius of any rectangle—finally, after 7 versions! However, even that doesn’t help us here. The results are still geometrically out of round.

So in InDesign, we come full circle to using Pathfinder to accomplish this task. Of course, even this beats manually splicing the two shapes together, which, more than 10 years ago, was the only choice for doing this.