CVPbkContactManager Class Reference

Destructor.

Commits all contacts in aContacts asynchronously.

See also: MVPbkStoreContact::CommitL

Compresses all stores asynchronously. NOTE: Not all stores are able to implement compression to their repositories.

Attribute manager is used for handling contact attributes like speed dialing or defaults.

The contact store list is used to handle a set of stores. After creation of manager the client can use the list to open all stores.

Copies all contacts in aContactLinks to aTargetStore asynchronously. If aTargetStore is NULL, contacts are copied to the store where they already are, ie. the contacts are duplicated.

Creates a new contact view specified by the view definition. The view can not be used before it has notified the observer that it is ready.

See also: CVPbkSortOrder

Creates an array of links corresponding to a packaged link or links. Packed links have been obtained by packing a link or a link array and they can be used for example for IPC but not for saving links. Loads the store plug-ins that are capable of creating the appropriate links.

See also: MVPbkContactLink::PackLC MVPbkContactLinkArray::PackLC

Internalizes a permanent link or links. An externalized link has been created using MVPbkStreamable interface from MVPbkContactLink. Loads the store plug-ins that are capable of creating the appropriate links.

See also: MVPbkContactLink::Streamable

Deletes contacts defined in link array asynchronously.

The contact manager owns a master list of field types that clients use. The store implementation then maps their native types to Virtual Phonebook types. Clients don't create field type objects themselves but use always references to types offered by this function.

Searches the contact stores for a contact that contains the given string in one of the field defined by given field type list asynchronously. NOTE: In some cases the find matches also other fields than those specified in aFieldTypes. Always loop through the results to check match in the required fields.

Finds a string containing text that is stored in one or more fields asynchronously. Client can give multiple find words. All the words must match to separated data. E.g. if there are two find words: "Jo" and "Jo" then field data "John Johnson" matches but "John Doe" doesn't if the word parser uses white space as a word separator.

NOTE: The accuracy of the results depends on the implementation of the store to carry out the find operation. The performance can also vary depending on the store.

Finds a string containing text that is stored in one or more fields asynchronously. Client can give multiple find words. All the words must match to separated data. E.g. if there are two find words: "Jo" and "Jo" then field data "John Johnson" matches but "John Doe" doesn't if the word parser uses white space as a word separator.

NOTE: The accuracy of the results depends on the implementation of the store to carry out the find operation. The performance can also vary depending on the store.

Returns the file server session of the contact manager.

Loads a store plug-in for given URI and adds aURI to the list of stores handled by this manager. If there is no store plug-in for the aURI then nothing changes.

Searches the contact stores for a phone number using defined amount of digits from the end of the number asynchronously. The store implementations determine, which field types are included in the search.

Creates a contact manager instance and loads the plug-ins that can handle the stores corresponding to the aURIList.

Creates a contact manager instance and loads the plug-ins that can handle the stores corresponding to the aURIList.

Retrieves asynchronously a contact that is individualized by a contact link. Delete the operation for canceling.