Contact Item Classes
The abstract base class for contact cards, templates and groups. All contact items are identified by a contact identifier TContactItemId , have a last modified date time, and own one or more fields the field set . Contact items also have an access count and attributes e.g. hidden . Note that fields in a contact item also have attributes. Attribute values specified in the contact item override those in the contained fields. The access count is a record of the number of objects referencing a...
Contacts Model API
As with other APIs covered in this book, we will not cover all aspects of the Contact Model. It is fully documented in Symbian OS SDKs, but the sheer volume of information can make it more difficult to get started than you might expect. In particular, this chapter will not cover classes and methods concerned with specialized database manipulation such as rollbacks and recovery , synchronization, field views and specialized phone number handling. CContactDatabase provides access to a Contact...
Handling Message Server Events
The final part of our messaging code is to handle events. The primary aim here is to pick up incoming messages without having to poll the mobile phone regularly. In fact, the Message Server provides us with events whenever a new message is created or a message is changed or deleted. Each time the event handler is called, we get a number of events reported. The messaging part of the code is relatively straightforward. If we have a new, changed or moved message, we verify that it is an SMS...
SCOM and BAL
SCOM is the higher-level API provided to manipulate devices and their filing systems. BAL the Bearer Abstraction Layer is a slightly lower-level API that manages device connection and disconnection and services on the device. SCOM uses BAL to provide its own API take a look at the respective device properties and the mapping will become apparent . It is possible to use SCOM without making direct use of BAL - indeed, this is how SCOM was originally intended to be used. However, the BAL service...
Obtaining Access to the Message Server and the SMS MTM
In order to write any messaging code, we will need to get a session with the Message Server. Like most good servers, the Message Server provides a good client API. The only requirement to obtain a Message Server session is an implementation of the MMsvSessionObserver mixin that includes a HandleSessionEventL method. As a minimum, we can address just those error events that mean we would lose access to the Message Server. class CRSmsCSServer public CCustomServer, public MMsvSessionObserver...