Qt Contacts C++ API

Main Classes

Contact Details Leaf Classes

Several subclasses of QContactDetail are provided as part of the Qt Contacts API. They are general in design but are intended to fulfill specific use-cases. Please note that certain backends may choose not to support one or more of these subclasses as they appear here; they may offer their own which provide similar functionality.

Each of these subclasses provide access to information stored in fields which may have certain constraints, documented in each subclass documentation.

Asynchronous Requests

Clients may use either the synchronous or asynchronous API to access functionality provided by a manager backend. The Qt Contacts Asynchronous API is offered through subclasses of the QContactAbstractRequest class:

Contact Selection

Clients may select a contact by specifying a unique contact id, or by supplying a QContactFilter which matches the contact or contacts they wish to select. The various derivatives of QContactFilter allow for fine-grained and flexible selection of contacts according to various criteria:

A client can also request that the results of such a selection be sorted, by passing a QContactSortOrder (or list of sort orders) to the manager.

Actions

Actions are described by descriptors and are instantiated by factories.

Backends

A backend implementor must implement the following interfaces:

For more information, see Qt Contacts Manager Engines.

Synchronization and Serialization

The Qt Contacts API is used by the Qt Versit module. It allows serialization of a QContact into a vCard document, and vice versa.