The destructor frees all resources owned by the field set, prior to its destruction.

Appends a field to the field set. The field set takes ownership of the field.

Gets the number of fields in the field set.

Externalises a CContactItemFieldSet object to a write stream.

Finds the first field in the field set with the specified field type.

Finds the first field in the field set containing both the content type mapping and the field type specified.

Finds the next field in the field set with the specified field type.

Finds the next field in the field set containing both the content type mapping and the field type specified.

Inserts a field into the field set.

Internalises a CContactItemFieldSet object from a read stream.

Find and return the index of the best matched template field. The method uses a matching algorithm which compares the content type of the template fields with that of the incoming contact item.

Matching Algorithm Steps: ========================

The algorithm is based on a scoring mechanism counting 'hits' and 'misses' in order to find the best possible field match within the fieldset of the template.

1. Loop through all the contact item fields of the template.

For each template field:

2. Perform a strict, or exact, match between the vCard mappings of the template field and the field to be matched. 3. If the vCard mappings match exactly, compare User Flags values and amend the overall score accordingly. 4. Loop through all the field types (TFieldType array) stored as part of the content type of the field to be matched.

For each field type of the field to be matched:

5. Loop through the field types of the iterated template field to find a field type match. Amend the 'hits' and 'misses' count accordingly. 6. Calculate the overall score weighing the 'hits' and 'misses' count. 7. Amend the overall score count in order to account for special cases (e.g. user defined fields) 8. Compare the overall score with the best score. If score > current best score, replace the 'bestScore' count and 'bestMatch' index.

9. Return the 'bestMatch' field index of the template field.

Changes a field's position within the field set.

Both indexes specified must be valid (i.e. between zero and Count()-1 inclusive), or the function raises a panic.

Allocates and constructs a new field set.

Allocates and constructs a new field set.

Get the first non-empty text field

Removes a field from the field set.

Deletes all fields in the field set.

Restores the field set using a view definition.

The overload that doesn't use dangerous CContactItemFieldSet::LoadTextStreamLC(aReadStream) method. LoadTextStreamLC relies on the stream to know its size, but now all types of streams support this functionality. In order to avoid calling LoadTextStreamLC, aTextBuf is already loaded in HBufC in the caller function. The caller function had access to the table and can use ColLength() API to get the lebgth of the field.

Stores the field set to a stream store.

Updates a field in the field set. The field whose content type matches aField's content type is replaced by aField. The second parameter is used to identify which matching field is updated. Specify 1 to update the first matching field, 2 for the second and so on. If there is no field in the field set which matches aField's content type, then aField is appended to the field set.

Updates a field in the field set. Searches the set for a matching field. Deletes the matching set's field if any. Adds the aField to the set anyway. Uses the IsEqualForSyncUpdate() function to compare two CContentType objects, rather than the default equals operator. Takes care to hold the PREF, VoiceDial, and SpeedDial properties in the updated field.

Gets the field located at a specified position in the field set.

Gets the field located at a specified position in the field set.