Some test text!

Create new form fields and widget annotations


Learn more accessing interactive fields
Understanding field types
Creating form fields

To create new form fields and widget annotations within a new document.

// Create a blank page
PDFDoc doc;
Page blank_page = doc.PageCreate();

// Create a new field (aka AcroForms).
Field emp_first_name = doc.FieldCreate("", Field::e_text, "John", "");

// Create text annotation
Annots::Widget annot = Annots::Widget::Create(doc, Rect(50, 550, 350, 600), emp_first_name);

// Add annotation to the page

// Add the page as the last page in the document.

PDF interactive forms (AcroForms)
Full code sample which illustrates some basic PDFNet capabilities related to interactive forms (also known as AcroForms).

linkLearn more accessing interactive fields

The form shown in the following figure consists of a number of Fields:

Every field has its name and value, as well as its annotation appearance.

In the PDFTron SDK, Fields are accessed through FieldIterators.

For example, the list of all Fields present in the document can be traversed using the following code snippet:

FieldIterator itr;
for(itr=doc.GetFieldIterator(); itr.HasNext(); itr.Next())
  Field field = itr.Current();
  printf("Field name: %s", field.GetName());

linkUnderstanding field types

PDF offers six different field types. Each type of form field is used for a different purpose, and they have different properties, appearances, options, and actions that can be associated with the fields. In this section, we will explain how to create all the seven field types and some attributes specific to each one.

Common field types are text-box, checkbox, radio-button, combo-box, and push-button. To find out the type of the Field use Field.GetType() method:

Field::Type type = field.GetType();
  case Field::e_button: 
  case Field::e_check: 
  case Field::e_radio: 
  case Field::e_text: 
  case Field::e_choice: 
  case Field::e_signature: 

linkCreating form fields

Regardless of which field type you create, you must provide a Field name:

Field my_field = doc.FieldCreate("address", Field::e_text);

Under most circumstances, field names must be unique. If you have a field you name as "address" and you create a second field you likewise call "address", you cannot supply different data in the two fields.

Field names can use alphanumeric characters to identify a field. All field names are case-sensitive. For example, you can use names such as empFirstName, empSecondName, empNumber, and so on for a group of fileds that are related to the same concept (in our sample employee entity).

Another technique for naming fields is to use a parent and child name. For example, you could name the above fields as follows:,, employee.number.

This naming convention is not only useful for organizing purposes but is well-suited for automatic operations on Fields. In the PDFTron SDK, Field.GetName() returns a string representing the fully qualified name of the field (e.g. ""). To get the child name ("first") use the Field.GetPartialName() method.

For more information about adding Fields, see the FDF code sample.

Get the answers you need: Support


Learn more accessing interactive fields
Understanding field types
Creating form fields