- You cannot get a handle to the default "Edit Batch Sequence" dialog that defines input/output locations concerning the PDFs you are trying to process. This is makes a kluge of things because I couldn't get a handle to the directories the user chose to process and output to as these are input fields on the dialog. I utilized the Acrobat SDK forums to verify my conclusions and my position was corroborated by an Adobe employee who monitors the forum. The only handle you have within the batch plug-in is that of the current document.
- The Acrobat API is adequately documented but only just so. If your C/C++ is rusty don't get frustrated. Take your time and read the documentation thoroughly. A hidden piece of documentation is the Adobe Dialog Manager API. This is what allows you to construct custom dialog boxes within Acrobat and is a separate document from the general SDK. The memset function is your friend and if you have forgotten, when using memset, memory is freed when the variable's scope is exited. Also refresh the memory on strcat, strncpy, strstr, strrchr, etc. Null terminate those char arrays and careful with functions like strncpy that do not null terminate automagically upon completion.
- Remember the Acrobat API is heavy on abstraction since it supports multiple OS types and multiple versions of these OS types.
Tuesday, September 13, 2011
Acrobat 9.0 Batch Plug-in for Enhanced Bates Numbering
I have completed the basic functionality of the enhanced Bates Numbering plug-in for Acrobat 9.0. I haven't tested the plug-in under version 10 yet. Recall that I needed enhanced logging in the instance where the files are renamed post Bates stamping. When a file is renamed I require the before and after names as well as complete path information for the respective files to be logged to a text file. A few interesting tidbits concerning this:
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment