The name of the plug-in is StartAut, because it is based on Starter.c
that is part of the AcroSDK. It was done using ATL (the ActiveX Template
Library). It does not use MFC. This proof-of-concept plug-in implements
a single object, "StartApp", and that object implements a single method,
"HelloWorld", which returns a string.
The subfolder "Test" contains a VB5 project that you can use to test the plug-in.
Since what we are doing is adding Automation capabilities to a plug-in,
which is not an executable, the way to access it from an Automation
controller is by first instantiating Acrobat, i.e.
CreateObject("AcroExch.App"), and then you can instantiate the object
exposed by the plug-in, in this example
CreateObject("StartApp.StartApp"). This is all demonstrated by the VB5
Also, registration is done every time that the plug-in gets loaded by
Acrobat, which means that you have to run Acrobat at least once with the
Start32.api in the plug_ins folder, before any controller will find it.
In your own plug-in, you may choose instead to do the registration from
within your installer.
The StartAut project uses PiMain.c, which is assumed to be in the
\pisdk\win directory. The project assumes that the rest of the files are
located in \Pub\Automate.
You will need to unzip the entire project into an Automate folder, and then unzip each of the embedded zipfiles into the folders StartAut, Test, and Win32. The project file can be found within the Win32 folder.
OK, so you want to stamp your document. Maybe you need to give reviewers some advice about the document's status or sensitivity. This tip from author Ted Padova demonstrates how to add stamps with the Stamp Tool along with related comments.