Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Exit
maxwyss
Advocate
maxwyss
Advocate
Activity
‎Jun 19, 2016
02:55 AM
1 Upvote
It is late in the discussion, but it must really be pointed out that creating a (fillable) form is much more than slapping some fields on the canvas (which is what "the Propaganda" makes you believe). This "much more" means analyzing the form's process, planning the form, planning the workflow, defining field naming, and so on. None of those points are handled with the field recognition. Conclusion: You have to work on the form anyway, so you better add the fields manually; you will save time with this. (sorry, "the Propaganda": you are simply wrong on this…). Hope this can help.
... View more
‎Jun 12, 2016
10:30 PM
Now add text to the field, move out of the field, get back in, delete the text, and move out again. If everything was done correctly, you now should see lines which were originally covered by the field. To confirm that, try with another field, and set the field's background to transparent as default.
... View more
‎Jun 11, 2016
11:35 PM
Zoom into the document, and see if the lines reappear. What you encounter is a rendering effect, where elements which are too small (too narrow) are not displayed. It is likely that you took the default width in Word, which translates to "hairline", which is a line, one pixel wide at screen resolution at 100%. This also means that the lines will disappear when you print the document. Always select a fixed width for your lines; preferrably 0.5 pt thick or more. Hope this can help.
... View more
‎Jun 11, 2016
11:30 PM
How did you secure the files? Did you set an owner password, where you restricted certain functions? If so, you are asked for that password only when you change the permissions. You do that in the Document properties, in the security tab where you change the setting to No Security. Change it, enter the password, when asked, and save the file under another name. Important advice: Always keep a copy of the unprotected, unrestricted file around. Hope this can help.
... View more
‎Jun 11, 2016
11:25 PM
This is a situation which has been around for a long time. One approach is to create those writing lines as part of the contents of the form (in other words, in the layout software). So, if the user prints the blank form, he has the writing lines. Now, if the form is filled on screen, those writing lines are more an annoyance than useful. And they are not needed, because text in a field will always be well aligned. With a little bit of JavaScript, we can have both options. In the Format event, you could add the following custom script: if (event.value.toString().length > 0) { event.target.fillColor = color.white ; } else { event.target.fillColor = color.transparent ; } If there is something in the field (the length of its value as string is greater than 0), the background of the field is white, and covers he writing lines. Otherwise, the background is transparent, and the lines are visible. Hope this can help.
... View more
‎Jun 10, 2016
10:12 PM
1 Upvote
You're welcome, Chris.crabb.simply. Well, you can get crap from any place, even the Ministry of Finance (trust me, I have my experiences with ministries of finances and/or national tax offices; they have a good solution, and then they decide to go for inferior crap…) Hmm… maybe they should let their developer where he is… FWIW, yours truly accepts CAD…
... View more
‎Jun 10, 2016
03:56 PM
2 Upvotes
I did a very quick analysis of the form, and these are my conclusions so far: • The form is Acroform • The form uses a bunch of spawned pages • The form is quite buggy (It crashed several times in Reader DC, but it was also able to bring up the Console with some error messages). It is possible that Acrobat DC is less tolerant than XI, when it comes to capitalization of functions of the Core Global Object. • The form has been saved "optimized for fast web view". Consequence is that it should not be viewed in a browser plug-in, but downloaded completely and opened locally. Doing a Save as… will also cause crashes, unless the form is closed immediately after the Save as… • There are (IMHO, way too) many small document-level JavaScripts. … and that's just the beginning… If the issuer of the form reads this, he is very welcome to contact me in private for a quote for debugging and optimizing the form…
... View more
‎Jun 07, 2016
11:00 PM
The procedure is exactly the same. What has changed is the place where to find the tools. In some ways, they are now easier to find, but if that fails you now can search for the tools. The JavaScript code is the same (although the author uses a method which has been deprecated for more than a decade, but is understood by Acrobat for backward compatibility purposes. Hope this can help.
... View more
‎Jun 07, 2016
08:34 AM
As it has been stated, in the Preferences, JavaScript tab. The first entry activates/deactivates JavaScript. (just don't forget to reactivate after you have done your tests). Hope this can help. Max Wyss.
... View more
‎Jun 07, 2016
05:54 AM
So, it is Acrobat, and positively NOT Adobe Reader. In this case, the "reader enabling" does not matter. There is a possibility that the form is set up to clear before saving (for example, if it MUST be printed … although a reset before save is extremely lame). It is, however also possible that the form gets reset upon opening, which is also common practice. Try opening the form with JavaScript deactivated, and see whether you still have the values.
... View more
‎Jun 07, 2016
05:30 AM
More details needed. Operating system and PDF viewer used by client, way the form was created, etc…
... View more
‎Jun 06, 2016
11:21 PM
You are not doing anything wrong. It is simple fact that the PDFMakers do not even attempt to convert the form elements to PDF. One thing you can try (note that I have not done that, so, it is an educated guess), is to get OpenOffice or LibreOffice, and see how far the Word form opens in that application. From there, you can export as PDF, and the fields with their properties should come through. The main suggestion, however, is to accept that you won't get the forms parts through, and take it as a chance to improve the form (I was even tempted to say, to "do the form right"…). Hope this can help.
... View more
‎Jun 05, 2016
04:47 PM
Well, you can see two definitions for the sum variable in this thread; how it will look in a particular case, I can't know; you would, however (because you know what the form should do at that particular place).
... View more
‎Jun 05, 2016
03:27 PM
Indeed, you are getting closer… You will, however, have to define the variable sum in the Calculate event before you can run these three lines. Thin it actually should work…
... View more
‎Jun 05, 2016
08:13 AM
You add "\r" for linebreaks. (if that does not lead to the desired result, use "\n" instead). Hope this can help.
... View more
‎Jun 05, 2016
08:11 AM
OK, time for another exercise, this time as a function… function somethingAndTheRest(inval, limit) { var a = math.min (inval, limit) ; if (a > limit) { return [limit, a - limit] ; } else { return [a, 0] ; } You call the function in this way (assuming you are going to look at the sum variable, an want it to be no greater than 8): var satr = somethingAndTheRest(sum, 8) ; this.getField("total").value = satr[0] ; this.getField("remainder").value = satr[1] ; Note that I have not tested the code, and therefore, it may have bugs. Hope this can help.
... View more
‎Jun 04, 2016
04:31 PM
Assuming that the total can not get beyond 79, you could do this: • Create a field for the remainder ("remainder") • Create a hidden, read-only field as carrier of the calculation ("calc"). • Rename (if needed) the field for the result to "total" • Add this script to Calculation event of the calc field: var f = this.getField("Text13") ; var g = this.getField("Text14") ; var j = this.getField("Text15") ; var sum = f.value*1 + g.value*1 + h.value*1 ; this.getField("total").value = 40 * Math.floor(sum / 40) ; this.getField("remainder").value = sum % 40 ; And that should do it. It might be recommended to use more reasonable field names for the summands, however. Hope this can help.
... View more
‎Jun 04, 2016
02:49 AM
In which form are those forms? Are they printed out, scanned and then processed using OCR, or are they filled out, and then either printed to PDF, or flattened as PDF? In any case, you would need to know the position of the field (in other words, its coordinates). There you would find the words, and — after applying some logic — you get the field values. Finally, you have to export that data in a form Excel can read (the most obvious one would be tab-delimited). Shameless plug: I have created such systems in the past; it is more than a weekend project, but works amazingly well. In case you consider buying over making, feel free to contact me in private for further discussions and quotes. Hope this can help.
... View more
‎Jun 03, 2016
05:37 PM
Math.max(a, b) returns the greater value of the two. Math.min(a, b) returns the smaller value of the two. (actually, you can pass more than two arguments, and it will return the greatest or smallest of them all). For your example, may I assume that the searched result is filled into field "TOTALDrinkingWaterCommitment". In this case, I would do the following var daSum = a.value*1 + b.value*1 + c.value*1 + d.value*1 ; event.value = Math.min(561073, Math.max(1090, daSum)) ; And that should do it (and I did count the parentheses…). Note the multiplication by 1 for the four summands. This forces the values to be numbers, so that they are actually added. Otherwise, as soon as one field is empty, the value would be the empty string, and instead of adding up, the numbers would be concatenated. …welcome to the great world of JavaScript…
... View more
‎Jun 03, 2016
05:28 PM
Thanks for the mention… Unfortunately, I can no longer edit the message; otherwise, I would have updated it.
... View more
‎Jun 03, 2016
03:21 PM
The color converting is a serious mess, because it has a considerable number of features covered only by either the dialog or JavaScript, but not both. You may check whether the convert color Preflight fixup would work, and then you could create a Preflight profile which you can call using JavaScript. Hope this can help.
... View more
‎Jun 03, 2016
03:14 PM
1 Upvote
The fundamental error in the coding is that the result should be compared with 400$, and not the population number value. Try this line: event.value = Math.max(400, (400 + ((a.value*1-10000) * 0.05)) ; and leave the fourth line away. Would this lead to the correct numbers?
... View more
‎May 31, 2016
02:49 AM
I guess you mean "fillable", and not "editable" (there's quite a difference between these two terms). Whether a fillable PDF is indeed fillable when viewed in a browser depends strictly on the PDF viewer used to display the document. The PDF viewing components coming with the common web browsers are too dumb to display fillable fields, and even more so to provide support for the logic behind the fields. State of the Art is using the Acrobat/Reader browser plug-in. However, fewer and fewer browsers support its architecture. Suggested workaround: Force download of the file, and open it in a suitable viewer, such as Acrobat/Reader. Hope this can help.
... View more
‎May 27, 2016
11:26 AM
That's pretty basic. You create for each product image a Button field (read-only, no action, icon only), and import your picture as icon of that field. And then you can show/hide that Button field like any other fields. Hope this can help.
... View more
‎May 27, 2016
06:19 AM
Which PDF viewer are you using on your iPad? What is the Action of the buttons? First and foremost, if you can't make it work from Acrobat, you won't even more so not be able to make it work from InDesign. The default PDF viewer on iDevices is extremely dumb (it can display PDFs, but fails with essentially any active element). The Adobe Reader for iDevices is not much smarter. You'd have the best chances that it works on your iPad by using PDF Expert by Readdle. Hope this can help.
... View more
‎May 21, 2016
10:28 AM
As already stated, that was possible in the first Acrobat versions. It was a decision by Adobe to break that feature. Of course, feel free to make an according feature request. And, if you want to save those $50, feel free to write your script; what you'd have to do is well described in this thread.
... View more
‎May 20, 2016
03:13 PM
Not having verified with the linked form, but the symptom of being "one step behind" usually means that the Calculation Order is not correct. Essentially, there is a field whose calculation depends on the result of another field, but that field's calculations are one after the one of the first field. Hope this can help.
... View more
‎May 18, 2016
02:27 AM
You're welcome Bachu. Acrobat JavaScript's capability is only very limited to find contents, and it would have to be within the cropbox anyway. So, if the page is cropped, contents outside of the cropbox is ignored. However, if you want to get rid of it before importing, you could set the mediabox of the page to the cropbox. That should get rid of such contents.
... View more
‎May 18, 2016
02:20 AM
Assuming that the field TodaysDate exists, you encounter a timing issue. At the time the function is executed, the fields have not yet been established. This is quite common with multipage forms. Therefore, you can define the function in a document-level script, but you will call it in the PageOpen event of the page at which the document opens. You may protect it, so that it runs only once. About the function, I have some doubts that it works, because you test whether the field value exists. This is always the case. Instead test whether the field's value is equal to the field's defaultValue. The function would then look like this: function populateDate() { if (this.getField("TodaysDate").value == this.getField("TodaysDate").defaultValue) { this.getField("TodaysDate").value = util.printd("m/d/yyyy", new Date() ; } } As stated, it is not even necessary to define the function, just execute the code in the pageOpen event. Hope this can help.
... View more
‎May 17, 2016
03:03 PM
1 Upvote
This is just the predictable and correct behavior. It is only Reader which depends on the Extended Rights. Acrobat can actively ignore them.
... View more
Copyright © 2024 Adobe. All rights reserved.
AdChoices