PDFdev is a service provided by PDFzone.com | http://www.pdfzone.com _____________________________________________________________
I don't consider implementing a race condition a viable option. Much as I'd like to easily run a script on document open, it appears I'll have to give up on this strategy. If I can't generate a FDF file from JavaScript that will cause the PDF to load the FDF before executing the JavaScript, then I'll still have to rely on my kludgy conditional code in the "PageOpen" code, to detect whether the document has just been opened. Thanks for trying, anyway. > -----Original Message----- > From: Ben Marchbanks [mailto:[EMAIL PROTECTED] > > IF you have no means to generate or append an FDF > file automatically outside Acrobat then this JavaScript > from FDF method is not a viable option. > > An alternative is to delay the document level javascript > for a specific time interval after the PDF opens or some > user intervention to run the Javascript post FDF import. > > You might simply use a setInterval() method that calls > the JavaScript after 5 seconds > > run = app.setInterval("YourJavaScript()", 5000) > > see the JavaScript User Guide for details... > > ----- Original Message ----- > From: "Karr, David" <[EMAIL PROTECTED]> > > > I haven't started to dig into this documentation yet, but I have a basic > question about this. > > > > Whatever we do with this will have to be limited to whatever we can do > in > plain Adobe JavaScript that we write in the Adobe Acrobat interface. Our > documents are downloaded from the web browser and viewed in the browser > with > Acrobat Reader. We also have operations in the document which generate and > route FDF files through email, which then routes the receiving user back > into the document through the browser and Acrobat Reader. > > > > So, can this modification to the generated FDF be done in plain Adobe > JavaScript without using native code? > > > > -----Original Message----- > > From: Ben Marchbanks [mailto:[EMAIL PROTECTED] > > > > The FDFtoolkit Reference documentation explains > > more about the /JavaScript and other keys and how to use them..... > > > > http://partners.adobe.com/asn/acrobat/forms.jsp > > > > ----- Original Message ----- > > From: "Karr, David" <[EMAIL PROTECTED]> > > > > > This is new to me. Could you be more specific about how this is done? > > Could you point me to a manual which describes this? > > > > > > -----Original Message----- > > > From: Ben Marchbanks [mailto:[EMAIL PROTECTED] > > > > > > You might include the JavaScript (call )in the FDF itself - > > > using the /Javascript key and specifying that it execute > > > after the import of the FDF.... > > > > > > /JavaScript << /After (YourDocumentLevel_JS(\);)>> > > > > > > ----- Original Message ----- > > > From: "Karr, David" <[EMAIL PROTECTED]> > > > > > > > > My colleague has found a problem with my approach of using the > > > > document-level JavaScript to perform the "DocOpen" event. > > > > > > > > We use PDF files in workflows, where the PDF is initially downloaded > and > > > > manipulated, and then the FDF file is routed through email. When > the > > > > user loads the FDF file, it's supposedly to implicitly load the PDF > file > > > > and then merge the fields in the FDF into the PDF. This process > > > > basically works, but what we're seeing is that when we load the PDF > by > > > > loading an FDF, it appears as if the document-level JavaScript is > > > > executing before the fields from the FDF file are merged into the > PDF. > > > > Is it expected that the scripts will execute before the FDF is > merged? > > > > Is there an easy way we can build the document so that the scripts > are > > > > executed AFTER the FDF data is merged in? To change your subscription: http://www.pdfzone.com/discussions/lists-pdfdev.html
