Settings and activity
15 results found
-
1 vote
An error occurred while saving the comment -
1 vote
Zachary Haber shared this idea ·
-
4 votesUnder review · 1 comment · Acrobat for Windows and Mac » Other · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment For the moment, I'm getting around this by using the batch-actions to run the preflight I want to, as that doesn't require the preflight library set in advance. Though it does require using batch actions instead of a user script or menu item.
-
4 votesUnder review · 2 comments · Acrobat for Windows and Mac » Other · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment An example of what I'd be looking for with this functionality:
For one batch action I'm looping over a document and creating different copies of the document with different annotation styles, but I can't "reduce file size" on it before creating each copy since it's a dynamic number of saves with some modifications between each.
The best I can do currrently is reduce/optimize the document in the steps before the Execute Javascript step, which unfortunately brings the file-size back up a little due to the changes in the annotations.
-
2 votes
An error occurred while saving the comment Ideally, this could come with a method in the JavaScript side that gets you the quads of the actual text itself instead of based on the line-height. This could either be another argument to Doc.getPageNthWordQuads or a separate method entirely.
An error occurred while saving the comment This would also be incredibly helpful with Redact annotations as well. There are times when simply Redacting a word will also end up wiping text above and below.
-
2 votes
An error occurred while saving the comment Having the ability continue working on other documents during any automatic batch processing would be really helpful. I've worked around this locally for my users by running Acrobat with `/n /s /o` commands which opens up acrobat in a new window/process, though it is still more problematic as they often have to remember to close down PDFs they aren't running in the batch action so they can re-open it in a new process.
-
2 votes
-
5 votes
-
2 votes
An error occurred while saving the comment You need to use the path `%APPDATA%\Adobe\Acrobat\DC\Preferences\Redaction\ENU\SearchRedactPatterns.xml`
Note: The only difference between this path and the one you used is the `Preferences` folder.
I'm not sure what the Redaction folder outside of the Preferences folder does, but evidentally it doesn't work for this..
-
2 votes
-
1 vote
An error occurred while saving the comment You can also do this via the JavaScript API as an action or just in the console:
// ensure that all annots are synced up
this.syncAnnotScan();
// Get all the annots in the document
const annots = this.getAnnots();
if (annots) {
// If there are annots, filter out the Redact types, and destroy them
annots
.filter((annot) => annot.type === "Redact")
.forEach(function (redact) {
redact.destroy();
});
} -
7 votes
-
2 votes
-
3 votes
-
158 votes
Hi All,
We have provided a registry protected fix, some users confirmed that this worked for them.
Could you please try this at your end as well and let us know your feedback?
Kindly make sure you are on the latest DC build(20.012.20043) and then follow the steps from the attached word file: “Steps.docx”.Regards,
ArvindAn error occurred while saving the comment I'm still seeing this issue today. For large documents with many comments (1000+), opening the comments tool freezes and crashes acrobat.
I tried the registry fix, and it's a definite improvement, but still not "quick" by any means, but it does mean Acrobat won't crash with basic interaction.
Is there any update on when a full fix will make it into Acrobat?
2022.001.20117 DC Continuous Release.
Windows 10 Pro 21H2 19044.1645
I'm not getting the error message in 22.002.20191.0 (x64) Windows.
But is it supposed to act as multiple thermometers when you call `thermometer.begin()` multiple times? Because for example, if you start a thermometer twice, you never get back to the "original" thermometer you started. With the current behavior I'd actually expect that the `t.end()` statement should close the thermometer in general, or it should restore the previous values before `thermometer.begin()` was called a second time. The current behavior is just confusing.
```
// Define the progress bar (thermometer) as a variable for easy reference
var t = app.thermometer;
// Start a progress bar
t.begin();
t.text = 'Therm Level 0'
t.duration = 50;
t.value = 1;
// Now start another progress bar
t.begin();
t.text = 'Therm Level 1'
t.duration = 100;
t.value = 90;
// Now end the top progress bar
t.end();
// Now see that the progress set on the original thermometer are overridden,
// But we still see the thermometer
```