He may have something there. He's not skipping the appearance generation, just the existing field parameter parsing to create the TextField.
> -----Original Message----- > From: Leonard Rosenthol [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 09, 2004 9:56 AM > To: "Robert Müller"; Paulo Soares; > [EMAIL PROTECTED] > Subject: RE: [iText-questions] AcroFields.setFields perfomance issues > > At 06:18 AM 12/9/2004, Robert Müller wrote: > >i tried AcroFields.setGenerateAppearances(false) but as i > have to "flatten" > >the form-fields and concatenate the generated pdfs i think > this won't work > >for me. > > Correct. You need to generate the appearance. > > > >or is the "content" of a text field more than just the text ? > > There are two parts to a field - the actual data > value and the > appearance (look) of the field. If you update the value but not the > appearance, then the user will see the OLD data (since that > is what would > be drawn by the appearance) EVEN THOUGH you had changed the value. > > It may be possible to optimize the appearance generation for > simple cases - but it is still a necessary process. > > > Leonard > > -------------------------------------------------------------- > ------------- > Leonard Rosenthol > <mailto:[EMAIL PROTECTED]> > Chief Technical Officer <http://www.pdfsages.com> > PDF Sages, Inc. 215-938-7080 (voice) > 215-938-0880 (fax) > > ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ iText-questions mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/itext-questions
