Symbian Developer Library

SYMBIAN OS V6.1 EDITION FOR C++

[Index] [Glossary] [Previous] [Next]



Location: msvapi.h
Link against: msgs.lib

Class MMsvEntryObserver

MMsvEntryObserver

Support

Supported from 5.0

Description

Provides the interface for notification of events associated with an entry. The types of event are given in the enumeration TMsvEntryEvent. Clients can provide an object that implements the interface, and set it to be notified through CMsvEntry::AddObserverL().

Defined in MMsvEntryObserver:
EMsvChildrenChanged, EMsvChildrenInvalid, EMsvChildrenMissing, EMsvContextInvalid, EMsvDeletedChildren, EMsvEntryChanged, EMsvEntryDeleted, EMsvEntryMoved, EMsvNewChildren, EMsvStoreCommitted, EMsvStoreCreated, EMsvStoreDeleted, HandleEntryEvent(), HandleEntryEventL(), TMsvEntryEvent


Event handler


HandleEntryEvent()

virtual void HandleEntryEvent(TMsvEntryEvent aEvent, TAny* aArg1, TAny* aArg2, TAny* aArg3)=0;

Support

Withdrawn in 5.1

Description

Indicates when called by a CMsvEntry object that an event has occurred — non-leaving. The type of event is indicated by the value of aEvent. The interpretation of the aArg1-3 values depends on this type.

For most event types, the action that is taken, for example, updating the display, is client-specific. Most clients will need to handle events that make the current context invalid: EMsvContextInvalid and EMsvEntryDeleted.

Parameters

TMsvEntryEvent aEvent

Indicates the event type.

TAny* aArg1-3

Event-specific argument values


HandleEntryEventL()

virtual void HandleEntryEventL(TMsvEntryEvent aEvent, TAny* aArg1, TAny* aArg2, TAny* aArg3)=0;

Support

Supported from 5.1

Description

Indicates when called by a CMsvEntry object that an event has occurred—can leave. The type of event is indicated by the value of aEvent. The interpretation of the aArg1-3 values depends on this type.

For most event types, the action that is taken, for example, updating the display, is client-specific. Most clients will need to handle events that make the current context invalid: EMsvContextInvalid and EMsvEntryDeleted.

An implementation can leave if an error occurs.

Parameters

TMsvEntryEvent aEvent

Indicates the event type.

TAny* aArg1-3

Event-specific argument values

[Top]


Enumerations


Enum TMsvEntryEvent

TMsvEntryEvent

Description

Defines entry event types.

EMsvEntryChanged

The entry has been changed, either as a result of a CMsvEntry::ChangeL() or by another client.

EMsvNewChildren

New children have been created. aArg1 points to a CMsvEntrySelection contain the ID of the new children.

EMsvDeletedChildren

Children have been deleted. aArg1 points to a CMsvEntrySelection contain the ID of the deleted children.

EMsvChildrenChanged

One or more of the children have been changed. aArg1 points to a CMsvEntrySelection containing the IDs of the changed children.

EMsvEntryDeleted

The entry has been deleted by another client. The context is now invalid.

EMsvContextInvalid

The context has become invalid. The entry has been changed, but the CMsvEntry was unable to update the context. The context will only become valid by a successful CMsvEntry::SetEntryL() call. aArg1 points to a TInt containing the error code for the invalid context.

EMsvChildrenMissing

Some new children have been created, but CMsvEntry was unable to retrieve the data from the Message Server. The children will be correct only after a successful call to CMsvEntry::SetEntryL().

EMsvChildrenInvalid

An error has occurred such that the status of the children is unknown and probably invalid. aArg1 points to a TInt containing the error code for the invalid context

EMsvStoreDeleted

The store associated with this entry has been deleted.

EMsvStoreCommitted

Changes to the store associated with this entry have been committed.

EMsvStoreCreated

A store associated with this entry has been created.

EMsvEntryMoved

The current entry has been moved by another client. The CMsvEntry has already been updated to reflect the new parent.