PDF-Forms is a service provided by PDFzone.com | http://www.pdfzone.com/ __________________________________________________________________
> According to the JavaScript Reference (AcroJS.pdf), > field.buttonImportIcon() is specifically noted as NOT working with Reader. As others have said, it has been around for a while. With respect to Reader, this method only allows you to import button appearances from PDFs, not any other file types. In order to import from other file types, the plug-in that's responsible for converting from those file types to PDF is required. In other words, pre-6 Reader could only import appearances from existing PDFs with this method. > Also, considering that such an operation would require modification of a document, > it would logically follow that it not be supported in Reader. I don't understand this logic. To me, it's simply filling-in a form field. Note that with Reader 6 you can still set button appearances via FDFs, which Reader is capable of loading (by launcing an FDF, via an 'Import form data' action, via HTTP, via stored document icons), you just can't use this particular method. If someone could explain the "security" concerns, I'd appreciate it. All this method does is set the button appearance to a page from a PDF that the user has access to (yes, and potentially submit the form, including button appearances, to a web server). I could understand restricting use of the cPath parameter, forcing the user to make a manual selection of the file and page, but why restrict it from Reader altogether? If it's a security concern, why only for Reader? George To change your subscription: http://www.pdfzone.com/discussions/lists-pdfforms.html
