steve poling wrote: > Consider that SignedBy field. It holds the same information as FromName, > and its stupid to ask for the same information twice. This is satisfied > by two text fields named FromName near the upper left hand corner of the > page and near the bottom of the page. This is less simple, but > tractible: Instantiate "parent" PdfFormField that we'll name FromName > and then instantiate "kid" TextField objects. You can use these kid > objects' GetTextField() function to get a kid PdfFormField object to > link to the parent via AddKid(). Then with parent and kids linked, we > can write the parents to the document.
Is that really necessary? You could add two fields with the exact same name, and most viewers (not all) will show the same value in both text boxes. This isn't very elegant as some viewers don't know what to do with two fields that share the same fully qualified name. My solution would be ta add a (read-only) text field that is updated automatically when the first field is entered. (Using JavaScript.) This is what the PDF reference says about tab order: PDF producers may make the navigation order explicit with the optional Tabs entry in a page object. The following are the possible values for this entry: * R (row order): Annotations are visited in rows running horizontally across the page. The direction within a row is determined by the Direction entry in the viewer preferences dictionary (see Section 8.1, "Viewer Preferences"). The first annotation visited is the first annotation in the topmost row. When the end of a row is encountered, the first annotation in the next row is visited. * C (column order): Annotations are visited in columns running vertically up and down the page. Columns are ordered by the Direction entry in the viewer preferences dictionary (see Section 8.1, "Viewer Preferences"). The first annotation visited is the one at the top of the first column. When the end of a column is encountered, the first annotation in the next column is visited. * S (structure order): Annotations are visited in the order in which they appear in the structure tree (see Section 10.6, "Logical Structure"). The order for annotations that are not included in the structure tree is application-dependent. The most elegant solution would be for us to implement this Tabs entry in the page dictionary (it's currently not supported in iText). -- This answer is provided by 1T3XT BVBA http://www.1t3xt.com/ - http://www.1t3xt.info ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ iText-questions mailing list iText-questions@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/itext-questions Buy the iText book: http://www.1t3xt.com/docs/book.php
