So, what were you using? Buttons? Checkboxes? From the description, it sounds like Checkboxes. In this case, open the PDF in Acrobat, switch to the form edit mode, select the checkbox(es), and display the properties. In the Appearance tab, you can set the border style and width, as well as the colors. Note that checkboxes have essentially 3 line widths (corresponding 1, 2, and 3 pt). Other values (0, 4 and higher) can be set using JavaScript, but may have unpredictible results. Now, if the appearance of the line is not "good enough", you could set the border to transparent, and scale the field so that the square when checked is positioned properly. That would use the line from the base document. However, you'd have to be very careful with positioning. Hope this can help. ... View more

Essentially, no. However, Adobe did seriously restrict the capabilities of Reader. In order to overcome those restrictions, Adobe developed the Extended Rights, and the according tools "Reader Extensions". The "full" Reader Extensions server was (and still is) sold for a very steep amount of money. There is, however, the possibility to add some extended Rights using Acrobat Pro. In this situation, there are limitations (such as 500 uses of that form). This was correct until Reader XI. Reader XI and newer no longer need the Extended Rights, and therefore, those limitations no longer apply. If you want to really be sure, read the Acrobat EULA. Hope this can help. ... View more

I am the author of the answer in the answers.acrobatusers.com forum message. There is not that much to add; just maybe to repeat. In Reader XI and newer, it is possible to spawn Template pages. It is also possible to delete spawned pages, but ONLY in the (Reader) session in which the page has been spawned. I am not quite sure whether even saving makes it impossible to delete. The page number encoded in the prefix of a spawned field is just a label; it does not have any logical connection to the page number of the spawned page. Let's say, you have spawned a page, and the prefix became P5, it does not matter whether the actual page is still page with logical page number 5; the fields work properly (this scenario could happen if you insert pages before that spawned page. The purpose of the rule of thumb why the page number in the prefix should not be greater than the actual logical page number is simply to prevent duplicate field names (when they should not be duplicated). The procedure to safely deal with spawning and deleting spawned pages is described in the forum message (save all field values, delete all spawned pages, respawn and refill the fields). Hope this can help. ... View more

Adobe Reader should at least show fields (although, if there is some JavaScript involved, it won't because it is too dumb); the other PDF viewers mentioned… forget it. Try PDF Expert by Readdle, which is considered to be the leader of the pack for iOS. Hope this can help. ... View more

Welcome to the new dimension of forms creating… What you want to accomplish can be done, using some little JavaScript. When your form is open in Acrobat DC, and the fields are set and tested, locate the JavaScript tools, and there select the Set Document Actions tool. A dialog will open, where you select the Document did Print entry, and click the Edit… button. A JavaScript editor window will open. There you enter this.resetForm() ; and then confirm all the dialogs and get back to the normal view. Don't forget to save the form. And that's about it. Hope this can help. ... View more

Do you get any error messages in the Console? ... View more

I am not sure whether you could do it as an action; it would not be much faster, but you could do other stuff while it runs. If you are on Mac, you could also create an Applescript which, if needed, uses System Events to accomplish the job; and if suitable, you could also create a droplet for that. A third thing to look closer (but I am not sure whether it does indeed exist) would be a Preflight fixup; here, you too, can create a droplet to automatize things. If suitable, converting to PDF/X1-a may also work. For a command line solution, you might contact for example Appligent, they may have a tool which would recreate the PDFs, and get rid of the Extended Rights. Hope this can help. ... View more

Which steps were you using to create the "Acrobat" version? What happens when you select (install beforehand, if needed) a PostScript printer (driver), and create a PostScript file, and then send it through Distiller? BTW, for comparing the results, it would be useful if the same area of the drawing would be shown at the same scale… ... View more

Sorry to hear that; it was a long shot. I know that my suggestion is not really acceptable (it would not be so for me…). Try reducing the screen size in the Windows system settings. This should make the texts become visible; you may also try changing the text size in the Windows system settings. It looks as if the text in the dialog does not scale properly, in relationship to the size of the icons (that's why I initially suggested to play with the display values in the Acrobat Preferences). As the Preflight tool is acquired software by Adobe, it is possible that some of the newest adjustments for screen size have not properly made it to that dialog… ... View more

As far as I know, it is not possible to predict the final file size, as file format and compression do depend a lot on the content of the images. A first step in the direction would be the Image Processor script. Hope this can help. ... View more

It may be a long shot, but have a look at the resolution values in the Page Display tab of the Preferences. Try setting it to either half or twice the value. Hope this can help. ... View more

This essentially means that the active layer does not have a textItem… I will have a closer look at the code later today. ... View more

OSX 10.11.3?? If so, then it is no surprise; Acrobat 7 is too old, and has components no longer supported since about OSX 10.9. As there is no upgrade path (as far as I know), you'd have to get Acrobat DC (either as a permanent license or as a subscription). Hope this can help. ... View more

You will need PDF Expert 5. If I remember correctly, the Enterprise version requires some back-end support. In order to see what PDF Expert supports JavaScript-wise, have a look at their support page. ... View more

It is possible that useAutoLeading has to be defined before it can be used. You might try to test whether it exists: if (lay.textItem.useAutoLeading == undefined) {alert("I don't know how to use useAutoLeading") } you may also test for the string "undefined" and/or for null. Or, you may also get all valid properties of your layer when you run the script from ExtendScript Editor, and have linked it to Photoshop, by using this code: for (var i in lay.textItem) {$.writeln(i + "  " + lay.textItem) } This will write all properties of your textItem and their values to the Console. Note: I have not tested the code, and it may therefore be buggy… Hope this can help. ... View more

It may actually be even better to avoid OCGs at all, and do everything with fields. Place the "contents" as the icon in a big button field, and the show/hide logic will become much simpler. ... View more

Maybe a dumb question, but do you make sure that the active layer is indeed a text layer? Could it also be that more than just the a textItem has to be specified in order to get access to the useAutoLeading property? ... View more

I think they did increase the area for resizing, and when the view of the checkbox is too small, there is no more space for the regular selection cursor to show. An immediate workaround is to zoom in somewhat, and then the regular selection cursor will appear. Alternatively, you can always move the field with the cursor keys, as stated. It is a feature, not a bug, and has to do with the whole frenzy of finger painting to work in Acrobat Pro (in other words, to make it work on small tablet-like computers). ... View more

Thanks, Madison. And for the record, the issues are solved for now. ... View more

Actually, Acrobat is (still) available as a perpetual license (you pay once, and that's it). The difference to the subscription model is that you will only get security updates (and maybe some features some product manager at Adobe considers to be worthy). For "better" updates, and the "services", you would have to shell out extra money. ... View more

It really depends on which version of OSX you have. Acrobat 7 is already very old, and Acrobat 8 is old. Both versions have lost support by Adobe a few years ago, and depending on the customer support person, you may simply be chased away when you ask for registration etc. of these versions. In the meantime, not only Adobe, but also Apple made changes in their architectures. One of those changes makes it no longer possible to create a PDF printer (in the sense of the AdobePS printer (driver))… if I remember correctly, that change happened some time in OSX 10.8. Also because Rosetta is no longer available and working, anything older than Acrobat 8 no longer works. In fact, I tried recently, but was not able to get Acrobat 8 running under OSX 10.10. The conclusion is, you may well have to bite into the sour apple and get the newest Acrobat (to limit immediate effect on cash, using the subscription system). This is not thaaat bad, because Acrobat DC is not the best Acrobat ever (that was Acrobat 5, IMHO), but still a good Acrobat. Hope this can help. ... View more

It depends a lot on which PDF viewer you are using. There are many PDF viewers out there which can display more or less properly a plain PDF (but if there are some overprinting or transparency pieces on the page, they may already fail). The PDF viewing components of the web browsers fall into this category. There are some who can actually display form fields, and allow entering data. Most of them do well, but there are some (actually, one in particular, namely Preview.app on OSX) which horrendously mess up the document when writing back. And then, there are few which do understand some actions and (Acrobat) JavaScript. The leader is Adobe Acrobat (because it is the PDF viewer with the longest history). However, as good as Acrobat is on Windows and Mac, it anything but that on iOS and Android. In fact, it is about the dumbest PDF viewer understanding a little bit of JavaScript. It is kind of common understanding that the leader for iOS is PDFExpert by Readdle, and for Android qPDF Notes Pro by Quoppa Software. Adobe completely missed the "mobile devices" train for PDF viewers. The conclusion is that you have to be aware of which PDF viewer your users are using, and you will have to create your forms for the dumbest one. You may actually end up in delivering your form dumbed down, and have a mechanism which activates the intelligent parts of your form when it opens, and the PDF viewer understands the command to do that. ... View more

Do you have the effect also when you display both pages together? ... View more

I played around a little bit with that file, and I can not repeat any of these effects. The Color Inspector shows that the rectangles all have the same color, and the color does NOT change when I delete and undelete the shape in darker blue. Could it be that the color management on your computer is not properly set up? (equipment used for the tests: MacBook Pro, OSX 10.10.5, Acrobat XI 11.0.09) Hope this can help. ... View more

I have not tested it, but it should work if you can start the selection outside of the highlighted text. ... View more

George_Johnson: For that reason, I also prefer flat. But this does not replace the lack of comment functionality (… as also found in the whole StackExchange universe, where it is even possible to comment on the question, and not just the answers…) ... View more

Thanks for the response, KJeryK. Will do so. ... View more

Thanks for rectifying, jane-e. It seems as if the fingers were faster than the eye… (I wish this forum had the comment functionality, as it was in the shot-down answers.acrobatusers.com forum(s)…) And by rereading the thread, and Judy's answer, it looks as if it is the same crappy PDF creation/saving engine Preview.app uses causing the issues… ... View more

If you hand't specified you were on OSX 10.11, I would have said you see an effect on Windows, where the preview function in the Windows File Explorer grabs the full access rights to the PDF. Could you check whether that file is somehow opened elsewhere (for example in Preview, or the Finder). ... View more