Absolutely correct, and it may lead to a considerable amount of preparing the document. So, it would need some justification to do so. ... View more

In the line of try67​'s comment, you would save the current span Object array (at latest in the onFocus Event), and compare the edited one with it in the Validation Event. Then you can reset the font sizes etc. A simplification is when the properties you want to control are all the same within the field; then you simply would reset those values in the span Object. ... View more

It may lead to other issues, but if you can replace the hyperlinks with fields, you would have more events at your disposal (such as MouseEnter and MouseExit, which would allow to show/hide other fields, and to load a premade graphic. ... View more

This does require some understanding of how PDF lays out pages, and (of course) of Acrobat JavaScript. Explaining it in detail would be beyond the scope of this forum, but could be done in a direct conversation. If interested in either learning how to do it, or have it delivered to you, feel free to contact me in private. ... View more

Some years ago, I had a similar task (with a few additional quirks, such as different pricing factors and different currencies). In that case, I first ran an analysing JavaScript over the document, locating and reading out prices. At the same location, it placed a form field, and set the underlying price as its default value. Then, a second script ran through the fields and calculated the price to display. Finally, a copy of the document got flattened. This was pretty straightforward. ... View more

From my experience, this procedure is suboptimal. In order to have control and the ability of a dynamic form (meaning to show/hide elements), I'd highly recommend to use form fields for the labels as well. ... View more

I think you are talking of the comb field property. ... View more

What is the problem with doing the hand and footwork yourself??? Actually, this is the only way to really get what you need. As good as the "field recognition" became in the meantime, it is a kludge. Adobe (and all form software makers) actively ignore the most important process when making a usable fillable form: the Analysis step. That's where you define things like field type, field name, formatting, etc. This is something you have to do; no software can do this for you. And then, actually implementing is no big deal at all. ... View more

Just to make it clear. You will not need PDFExpert to create the forms; you will create (and maintain) the forms with Acrobat. Only the engineers filling the forms on the iPads will need PDFExpert. (well, you may need a copy too, for testing purposes). I personally do not have a working iPad, but a business partner of mine tests everything I create on his iPad using PDFExpert. ... View more

This would be possible, but most likely be beyond "Acrobat Reader" for iOS' capabilities. You (your client) would have to get a better PDF viewer on the engineers' iPads (PDFExpert by Readdle is considered to be the leader of the pack). The implementation would be to have a JavaScript setting the fields to be protected to readonly, when the saving or sending button is tapped (before the actual saving or sending, of course). ... View more

Would work as well. ... View more

Does it reject accented latin characters in the Arabic field? ... View more

A rule of thumb is to be rather generous with the field size, and position it accordingly. And then test it on all the platforms you want to use. Just from the screenshot, it shows that your field is too low; try entering "fgfgfg" and see how it looks. Just about every PDF Viewer displaying form fields has a different way to render the contents, and to place the baseline of the text. C'est la vie! ... View more

A possibility to get rid of cached information would be to reset the form when it gets opened. If it is a single-page form, it is very easy: In the PageOpen Script, you add the following line of code:      this.resetForm() ; and that does it. If it is a multiple page form, you have to make sure that the reset gets executed only once. For that, you create a document-level script containing just this line of code:      var loaded = 1 ; And in the Page Open event of the page at which the document opens, you add this:      if (loaded > 0) {      this.resetForm() ;      loaded -- ;      } And that should do it. ... View more

… and how old is Reader X??? ... View more

The problem is, IMHO, that there are valid accented letters in English, and (assuming) valid latin letters in Arabic text. That would have to be taken care of with additional logic. An additional question is how to treat numbers, particularly if you want to have some calculations involved. ... View more

George and "Test Screen Name" are kind of correct. If you just want to viszally display something, you don't need a Keystroke event script, and you can do the character filtering in the Format event. HOWEVER, if you want to do something with the value, you will already have to make sure that only legal characters are entered. Otherwise, you will have garbage input into your further calculations. A very simplistic approach is to make sure you work with a string, and then use the replace() function with an according Regular Expression. In the Keystroke Event, you would use this script:      if (!event.willCommit) {      event.change = event.change.toString().replace(/[^\d.]/gim, "") ;      } This will drop any entered character, except numbers, the minus sign and the period. Then you can use the already mentioned script in the Format event. ... View more

Well, it is a bit of a challenge to make something work on iDevices, and I fully agree that there are quite a few things even the best PDF Viewer for iOS does not support. The question is, why did, for example, Adobe such a lousy job with their PDF Viewer for iOS (and an even worse one for Android)?? ... View more

You appear stuck with semantics here. In the days before the mobile phone frenzy, what the OP calls "app" was often called "lightweight application" (but for today's users, that has too many syllables…) Otherwise, what would you call, for example my booking system for small enterprises in the hotellerie or para-hotellerie, coming along as a 1.2 MB PDF? It is not a form (although it uses Acroforms as a base), so it must be some kind of app, but according your definition, it is not, because it has not been created in Visual Studio (BTW, on Mac, one would use Xcode…). So, what is it? ... View more

I just wonder how many Mac-based developers are using Visual Studio. If anything, it would have to be a connection to Xcode. … or support for BBEdit. Looks to me as if they listened to some big-enterprise market research companies. ... View more

I have 10.14 on a virtual machine, and I will check it out shortly. However, what happens when you run the script directly from ExtendScript Toolkit (and not saved and out of Photoshop)? ... View more

Folder.userData should resolve to ~/Library/Application Support/ (or if you get it as URL ~/Library/Application%20Support) What you could do is get ExtendScript Toolkit, and hook it up with your Photoshop version, and run (for example) the following script: alert(Folder.userData) Photoshop should then come to the foreground and display an alert containing the path. It is, however, possible that the error is caused by Apple's messing around with interapplication communication in 10.14 (and it is getting worse and worse with every new version) ... View more

On Mac (as mentioned), a Droplet is an .app Bundle, containing a specific structure of subfolders and files. Therefore, it won't open in a text editor. ... View more

It may be a bit on a tangent, and I noticed very late that the thread is very old, but nevertheless would there be any way to get the Action out of a Droplet (I am looking at the Mac variant)? Thanks ... View more

Finally, for existing images, you might use exiftool to scrub all metadata. ... View more

It is a bit speculative, and would need verification… One aspect is that Photoshop/Camera RAW treats RAW files as if they were read-only (even if the permissions would allow writing). This affects metadata, and for that reason, the metadata must be carried externally (in the .XMP file). Another aspect is that Camera RAW writes many custom tags (crs: group) into the metadata. I can not confirm whether Photoshop/Camera RAW would be able to read those tags from the image file's metadata, and even more so writing them properly (even if it would treat the image files as writeable). Other image formats (JPEG, TIFF, PSD) can be considered derivative formats from the RAW format. These formats are not considered to be read-only, and Photoshop is free to write metadata directly into the file. However, because the crs: tags are only of interest for the RAW format, PS would neither use nor write those tags in connection with those file formats. Note that the crs: tags from the Camera RAW plug-in are the reason why we can do non-destructive processing of the RAW images. Actually using the XMP sidecar file opens some very interesting possibilities (which are to some extent implemented in Lightroom). ... View more

C'était déjà mentionné, si une version de PS n'est plus supportée avec une nouvelle version de Camera RAW, il faut utiliser le DNG Converter dans sa version la plus récente. Les fichiers DNG peuvent être procédés avec les versions anciens de PS. ... View more

The RegExp Object is part of the JavaScript Core, and very often not described in specific variants of JavaScript. You might look at a general JavaScript documentation which does include the Core. ... View more

From where do you call the script? ... View more