CBaseMtmUi Class Reference

class CBaseMtmUi : public CBase

Provides MTM-specific user interaction, such as editing, viewing, deleting, and copying of message entries.

Message client applications use the class to access such functionality polymorphically. MTM implementers implement a derived class to provide such functionality for their message protocol.

The base class is largely an interface definition: it implements little important functionality itself. For implementers, this documentation defines conditions that any implementation must fulfil, plus suggested semantics for behaviour. This still leaves many decisions in the hands of the implementer. A key design time activity is to define how the particular characteristics of the implemented protocol are best mapped to the interface. As this class is concerned with user interfaces, implementers should be sensitive to the look and feel of the target phone.

Many functions are required to return an instance of a CMsvOperation-derived class to provide asynchronous control and monitoring to the caller of the operation being performed.

The following are some significant groups of functions:

Entry manipulation functions: OpenL(), CloseL(), EditL(), and ViewL() are all available in two overloaded versions. The first version operates on the current context. The second version operates upon groups of entries specified by a CMsvEntrySelection argument. All entries must be in same folder and all of the correct MTM type. The context may change after calling these functions. Concrete User Interface MTMs can legally ignore any of the entries within the selection - many may, for example, simply open the first entry.

Copying and moving functions: the CopyToL(), CopyFromL(), MoveToL(), and MoveFromL() functions are concerned with copying and moving entries to and from remote servers. MTMs can implement these functions to provide any user interaction needed before copying or moving can proceed, such as dialogs to confirm settings; and, any protocol-specific setup steps that can be done at this stage: for example, a fax MTM could render messages into the required image format.

Progress information functions: DisplayProgressSummary() and GetProgress() convert MTM-specific progress information about some asynchronous operation, such as message sending, to a human-readable form. The progress information to pass into these functions is, in general, obtained from an on-going CMsvOperation by calling CMsvOperation::Progress(). The nature of any information provided is MTM-specific.

MTM-specific UI functions: MTM components can offer protocol-specific functionality not provided by base class interface functions. MTM components define IDs that correspond to each protocol-specific operation offered, and implement the InvokeSyncFunctionL() and InvokeAsyncFunctionL() functions to allow clients to access these operations by passing in the appropriate ID. Two functions are provided to allow the MTM component to offer both synchronous and asynchronous functionality. Message client applications can dynamically add user-interface features for these operations using CBaseMtmUiData::MtmSpecificFunctions(). MTM developers should document the IDs if they wish to make the operations available to clients.

Inherits from

Public Member Functions
~CBaseMtmUi()
IMPORT_C CBaseMtm &BaseMtm()
CMsvOperation *CancelL(TRequestStatus &, const CMsvEntrySelection &)
CMsvOperation *CloseL(TRequestStatus &)
CMsvOperation *CloseL(TRequestStatus &, const CMsvEntrySelection &)
IMPORT_C CMsvOperation *CopyFromL(const CMsvEntrySelection &, TMsvId, TRequestStatus &)
IMPORT_C CMsvOperation *CopyToL(const CMsvEntrySelection &, TRequestStatus &)
IMPORT_C CMsvOperation *CreateL(const TMsvEntry &, CMsvEntry &, TRequestStatus &)
IMPORT_C CMsvOperation *DeleteFromL(const CMsvEntrySelection &, TRequestStatus &)
IMPORT_C CMsvOperation *DeleteServiceL(const TMsvEntry &, TRequestStatus &)
IMPORT_C TIntDisplayProgressSummary(const TDesC8 &)
CMsvOperation *EditL(TRequestStatus &)
CMsvOperation *EditL(TRequestStatus &, const CMsvEntrySelection &)
CMsvOperation *ForwardL(TMsvId, TMsvPartList, TRequestStatus &)
IMPORT_C TIntGetProgress(const TDesC8 &, TBuf< EProgressStringMaxLen > &, TInt &, TInt &, TInt &, TInt &)
IMPORT_C CMsvOperation *InvokeAsyncFunctionL(TInt, const CMsvEntrySelection &, TRequestStatus &, TDes8 &)
IMPORT_C voidInvokeSyncFunctionL(TInt, const CMsvEntrySelection &, TDes8 &)
IMPORT_C CMsvOperation *MoveFromL(const CMsvEntrySelection &, TMsvId, TRequestStatus &)
IMPORT_C CMsvOperation *MoveToL(const CMsvEntrySelection &, TRequestStatus &)
CMsvOperation *OpenL(TRequestStatus &)
CMsvOperation *OpenL(TRequestStatus &, const CMsvEntrySelection &)
IMPORT_C TUintPreferences()
IMPORT_C TIntQueryCapability(TUid, TInt &)
CMsvOperation *ReplyL(TMsvId, TMsvPartList, TRequestStatus &)
IMPORT_C voidSetPreferences(TUint)
IMPORT_C TUidType()
IMPORT_C CMsvOperation *UnDeleteFromL(const CMsvEntrySelection &, TRequestStatus &)
CMsvOperation *ViewL(TRequestStatus &)
CMsvOperation *ViewL(TRequestStatus &, const CMsvEntrySelection &)
Protected Member Functions
CBaseMtmUi(CBaseMtm &, CRegisteredMtmDll &)
IMPORT_C voidConstructL()
IMPORT_C TAny *GetInterface(TUid)
voidGetResourceFileName(TFileName &)
IMPORT_C CMsvSession &Session()
Inherited Functions
CBase::CBase()
CBase::Delete(CBase *)
CBase::Extension_(TUint,TAny *&,TAny *)
CBase::operator new(TUint)
CBase::operator new(TUint,TAny *)
CBase::operator new(TUint,TLeave)
CBase::operator new(TUint,TLeave,TUint)
CBase::operator new(TUint,TUint)
CBase::~CBase()
Public Member Enumerations
enumanonymous { EProgressStringMaxLen = 255 }
Protected Attributes
CBaseMtm &iBaseMtm
CCoeEnv *iCoeEnv
TUint iFlags
Private Attributes
TAny *iExtensionData
CRegisteredMtmDll &iRegisteredMtmDll
TInt iResourceFileOffset

Constructor & Destructor Documentation

CBaseMtmUi(CBaseMtm &, CRegisteredMtmDll &)

IMPORT_CCBaseMtmUi(CBaseMtm &aBaseMtm,
CRegisteredMtmDll &aRegisteredMtmDll
)[protected]

Parameters

CBaseMtm & aBaseMtm
CRegisteredMtmDll & aRegisteredMtmDll

~CBaseMtmUi()

IMPORT_C~CBaseMtmUi()[virtual]

Member Functions Documentation

BaseMtm()

IMPORT_C CBaseMtm &BaseMtm()const

CancelL(TRequestStatus &, const CMsvEntrySelection &)

CMsvOperation *CancelL(TRequestStatus &aStatus,
const CMsvEntrySelection &aSelection
)[pure virtual]

Cancels the sending of specified messages.

leave

KErrNotSupported The User Interface MTM does not support cancel operations, or cancelling is inappropriate to the current context

leave

Other Dependent on implementation

If successful, this is an asynchronously completing cancel operation. If failed, this is a completed operation, with status set to the relevant error code.

Parameters

TRequestStatus & aStatusThe request status to be completed when the operation has finished
const CMsvEntrySelection & aSelectionSelection of message entries

CloseL(TRequestStatus &)

CMsvOperation *CloseL(TRequestStatus &aStatus)[pure virtual]

Closes an entry. The behaviour that this implies is dependent on the current context:

1. for message contexts, this usually closes any launched editors or viewers

2. for folder contexts, leaves with KErrNotSupported

3. for service contexts, causes closure of a connection to a server

The returned CMsvOperation object completes when closing is complete.

Requirements:

Implementations should:

1. check aEntry.iType.iUid to ensure that they can close the requested type of entry and leave with code KErrNotSupported if they cannot

2. return a CMsvOperation-derived object to provide asynchronous control and monitoring of the operation

leave

KErrNotSupported The User Interface MTM does not support close operations, or closing is inappropriate to the current context

leave

Other Dependent on implementation

If successful, this is an asynchronously completing close operation. If failed, this is a completed operation, with status set to the relevant error code.

Parameters

TRequestStatus & aStatusThe request status to be completed when the operation has finished

CloseL(TRequestStatus &, const CMsvEntrySelection &)

CMsvOperation *CloseL(TRequestStatus &aStatus,
const CMsvEntrySelection &aSelection
)[pure virtual]

Closes a selection of entries.

The behaviour that this implies is dependent on the current context:

1. for message contexts, this usually closes any launched editors or viewers

2. for folder contexts, leaves with KErrNotSupported

3. for service contexts, causes closure of a connection to a server

The returned CMsvOperation object completes when closing is complete.

Requirements:

Implementations should:

1. check aEntry.iType.iUid to ensure that they can close the requested type of entry and leave with code KErrNotSupported if they cannot

2. return a CMsvOperation-derived object to provide asynchronous control and monitoring of the operation

leave

KErrNotSupported The User Interface MTM does not support close operations, or closing is inappropriate to the current context

leave

Other Dependent on implementation

If successful, this is an asynchronously completing close operation. If failed, this is a completed operation, with status set to the relevant error code.

Parameters

TRequestStatus & aStatusThe request status to be completed when the operation has finished
const CMsvEntrySelection & aSelectionSelection of message entries

ConstructL()

IMPORT_C voidConstructL()[protected, virtual]

CopyFromL(const CMsvEntrySelection &, TMsvId, TRequestStatus &)

IMPORT_C CMsvOperation *CopyFromL(const CMsvEntrySelection &aSelection,
TMsvIdaTargetId,
TRequestStatus &aStatus
)[virtual]

Parameters

const CMsvEntrySelection & aSelection
TMsvId aTargetId
TRequestStatus & aStatus

CopyToL(const CMsvEntrySelection &, TRequestStatus &)

IMPORT_C CMsvOperation *CopyToL(const CMsvEntrySelection &aSelection,
TRequestStatus &aStatus
)[virtual]

Parameters

const CMsvEntrySelection & aSelection
TRequestStatus & aStatus

CreateL(const TMsvEntry &, CMsvEntry &, TRequestStatus &)

IMPORT_C CMsvOperation *CreateL(const TMsvEntry &aEntry,
CMsvEntry &aParent,
TRequestStatus &aStatus
)[virtual]

Parameters

const TMsvEntry & aEntry
CMsvEntry & aParent
TRequestStatus & aStatus

DeleteFromL(const CMsvEntrySelection &, TRequestStatus &)

IMPORT_C CMsvOperation *DeleteFromL(const CMsvEntrySelection &aSelection,
TRequestStatus &aStatus
)[virtual]

Parameters

const CMsvEntrySelection & aSelection
TRequestStatus & aStatus

DeleteServiceL(const TMsvEntry &, TRequestStatus &)

IMPORT_C CMsvOperation *DeleteServiceL(const TMsvEntry &aService,
TRequestStatus &aStatus
)[virtual]

Parameters

const TMsvEntry & aService
TRequestStatus & aStatus

DisplayProgressSummary(const TDesC8 &)

IMPORT_C TIntDisplayProgressSummary(const TDesC8 &aProgress)const [virtual]

Parameters

const TDesC8 & aProgress

EditL(TRequestStatus &)

CMsvOperation *EditL(TRequestStatus &aStatus)[pure virtual]

Edits an entry.

The behaviour that this implies is dependent on the current context:

1. for message contexts, this usually launches the appropriate message editor, or returns status KErrReadOnly if the message is not editable

2. for remote folder contexts, launches a settings dialog, for example to rename the folder, completing asynchronously

3. for service contexts, launches a service settings dialog, completing asynchronously

The returned CMsvOperation object completes when editing is complete.

Requirements:

Implementations should:

1. check aEntry.iType.iUid to ensure that they can edit the requested type of entry and leave with code KErrNotSupported if they cannot

2. return a CMsvOperation-derived object to provide asynchronous control and monitoring of the operation

3. for remote messages, typically, copy the messages to the Inbox

4. follow the leave protocols described in Leave considerations below

leave

KErrNotSupported The User Interface MTM does not support edit operations, or editing is inappropriate to the current context

leave

KErrReadOnly Context is read-only

leave

Other Dependent on implementation

If successful, this is an asynchronously completing edit operation. If failed, this is a completed operation, with status set to the relevant error code.

Parameters

TRequestStatus & aStatusThe request status to be completed when the operation has finished

EditL(TRequestStatus &, const CMsvEntrySelection &)

CMsvOperation *EditL(TRequestStatus &aStatus,
const CMsvEntrySelection &aSelection
)[pure virtual]

Edits a selection of entries.

The behaviour that this implies is dependent on the current context:

1. for message contexts, this usually launches the appropriate message editor, or returns status KErrReadOnly if the message is not editable

2. for remote folder contexts, launches a settings dialog, for example to rename the folder, completing asynchronously

3. for service contexts, launches a service settings dialog, completing asynchronously

The returned CMsvOperation object completes when editing is complete.

Requirements:

Implementations should:

1. check aEntry.iType.iUid to ensure that they can edit the requested type of entry and leave with code KErrNotSupported if they cannot

2. return a CMsvOperation-derived object to provide asynchronous control and monitoring of the operation

3. for remote messages, typically, copy the messages to the Inbox

4. follow the leave protocols described in Leave considerations below

leave

KErrNotSupported The User Interface MTM does not support edit operations, or editing is inappropriate to the current context

leave

KErrReadOnly Context is read-only

leave

Other Dependent on implementation

If successful, this is an asynchronously completing edit operation. If failed, this is a completed operation, with status set to the relevant error code.

Parameters

TRequestStatus & aStatusThe request status to be completed when the operation has finished
const CMsvEntrySelection & aSelectionSelection of message entries

ForwardL(TMsvId, TMsvPartList, TRequestStatus &)

CMsvOperation *ForwardL(TMsvIdaDestination,
TMsvPartListaPartList,
TRequestStatus &aCompletionStatus
)[pure virtual]

Creates a forwarded message from the current message context, and allows the user to edit it through a message-type specific editor.

Some MTMs may support inclusion of elements, specified by aPartlist, from the original message in the forwarded message. The parent for the new entry is specified in aDestination. The returned CMsvOperation object completes when editing the forwarded message is complete. On completion, the context is set to the forwarded message.

Requirements:

A typical implementation for this function would include the following steps:

1. create a new forwarded message entry by calling CBaseMtm::ForwardL()

2. call EditL() allow the user to edit the forwarded message

3. return a CMsvOperation-derived object to provide asynchronous control and monitoring of the operation

If forwarded messages are not supported, implementations should leave with KErrNotSupported.

If successful, this is an asynchronously completing forward message operation. If failed, this is a completed operation, with status set to the relevant error code.

leave

KErrNotSupported The User Interface MTM does not support message forwarding operations

leave

Other Dependent on implementation

Parameters

TMsvId aDestinationThe entry to which to assign the forwarded message
TMsvPartList aPartListDefines the parts which are to be copied from the original message into the forwarded message
TRequestStatus & aCompletionStatusThe request status to be completed when the operation has finished

GetInterface(TUid)

IMPORT_C TAny *GetInterface(TUidaUid)[protected, virtual]

Parameters

TUid aUid

GetProgress(const TDesC8 &, TBuf< EProgressStringMaxLen > &, TInt &, TInt &, TInt &, TInt &)

IMPORT_C TIntGetProgress(const TDesC8 &aProgress,
TBuf< EProgressStringMaxLen > &aReturnString,
TInt &aTotalEntryCount,
TInt &aEntriesDone,
TInt &aCurrentEntrySize,
TInt &aCurrentBytesTrans
)const [virtual]

Parameters

const TDesC8 & aProgress
TBuf< EProgressStringMaxLen > & aReturnString
TInt & aTotalEntryCount
TInt & aEntriesDone
TInt & aCurrentEntrySize
TInt & aCurrentBytesTrans

GetResourceFileName(TFileName &)

voidGetResourceFileName(TFileName &aFileName)const [protected, pure virtual]

Sets the full path and name of the resource file associated with the User Interface MTM.

Client applications do not use this function. It is relevant only to implementers of derived classes.

Requirements:

The function is called by CBaseMtmUi::ConstructL(), which then loads the resource file.

Parameters

TFileName & aFileNameFilename buffer to be filled with the resource file path and name

InvokeAsyncFunctionL(TInt, const CMsvEntrySelection &, TRequestStatus &, TDes8 &)

IMPORT_C CMsvOperation *InvokeAsyncFunctionL(TIntaFunctionId,
const CMsvEntrySelection &aSelection,
TRequestStatus &aCompletionStatus,
TDes8 &aParameter
)[virtual]

Parameters

TInt aFunctionId
const CMsvEntrySelection & aSelection
TRequestStatus & aCompletionStatus
TDes8 & aParameter

InvokeSyncFunctionL(TInt, const CMsvEntrySelection &, TDes8 &)

IMPORT_C voidInvokeSyncFunctionL(TIntaFunctionId,
const CMsvEntrySelection &aSelection,
TDes8 &aParameter
)[virtual]

Parameters

TInt aFunctionId
const CMsvEntrySelection & aSelection
TDes8 & aParameter

MoveFromL(const CMsvEntrySelection &, TMsvId, TRequestStatus &)

IMPORT_C CMsvOperation *MoveFromL(const CMsvEntrySelection &aSelection,
TMsvIdaTargetId,
TRequestStatus &aStatus
)[virtual]

Parameters

const CMsvEntrySelection & aSelection
TMsvId aTargetId
TRequestStatus & aStatus

MoveToL(const CMsvEntrySelection &, TRequestStatus &)

IMPORT_C CMsvOperation *MoveToL(const CMsvEntrySelection &aSelection,
TRequestStatus &aStatus
)[virtual]

Parameters

const CMsvEntrySelection & aSelection
TRequestStatus & aStatus

OpenL(TRequestStatus &)

CMsvOperation *OpenL(TRequestStatus &aStatus)[pure virtual]

Opens an entry.

The behaviour that this implies is dependent on the current context:

1. for message contexts, OpenL() is the equivalent of EditL(), or for read-only messages, ViewL(). Whether opening of remote messages is allowed is MTM-specific.

2. for service contexts, the function may initiate a connection to obtain the service contents from the server, completing asynchronously

3. for remote folder contexts, dependent on implementation, the function may initiate a connection to obtain the folder contents from the server, completing asynchronously

The returned CMsvOperation object completes when opening is complete.

Requirements:

If opening entries is not supported, implementations should leave with KErrNotSupported. Otherwise, implementations should:

1. check aEntry.iType.iUid to ensure that they can open the requested type of entry and leave with code KErrNotSupported if they cannot

2. return a CMsvOperation-derived object to provide asynchronous control and monitoring of the operation

3. for remote messages, typically, copy the messages to the Inbox

leave

KErrNotSupported The User Interface MTM does not support open operations, or opening is inappropriate to the current context

leave

Other Dependent on implementation

If successful, this is an asynchronously completing open operation. If failed, this is a completed operation, with status set to the relevant error code.

Parameters

TRequestStatus & aStatusThe request status to be completed when the operation has finished

OpenL(TRequestStatus &, const CMsvEntrySelection &)

CMsvOperation *OpenL(TRequestStatus &aStatus,
const CMsvEntrySelection &aSelection
)[pure virtual]

Opens a selection of entries.

The behaviour that this implies is dependent on the current context:

1. for message contexts, OpenL() is the equivalent of EditL(), or for read-only messages, ViewL(). Whether opening of remote messages is allowed is MTM-specific.

2. for service contexts, the function may initiate a connection to obtain the service contents from the server, completing asynchronously

3. for remote folder contexts, dependent on implementation, the function may initiate a connection to obtain the folder contents from the server, completing asynchronously

The returned CMsvOperation object completes when opening is complete.

Requirements:

If opening entries is not supported, implementations should leave with KErrNotSupported. Otherwise, implementations should:

1. check aEntry.iType.iUid to ensure that they can open the requested type of entry and leave with code KErrNotSupported if they cannot

2. return a CMsvOperation-derived object to provide asynchronous control and monitoring of the operation

3. for remote messages, typically, copy the messages to the Inbox

leave

KErrNotSupported The User Interface MTM does not support open operations, or opening is inappropriate to the current context

leave

Other Dependent on implementation

If successful, this is an asynchronously completing open operation. If failed, this is a completed operation, with status set to the relevant error code.

Parameters

TRequestStatus & aStatusThe request status to be completed when the operation has finished
const CMsvEntrySelection & aSelectionSelection of message entries

Preferences()

IMPORT_C TUintPreferences()const

QueryCapability(TUid, TInt &)

IMPORT_C TIntQueryCapability(TUidaCapability,
TInt &aResponse
)[virtual]

Parameters

TUid aCapability
TInt & aResponse

ReplyL(TMsvId, TMsvPartList, TRequestStatus &)

CMsvOperation *ReplyL(TMsvIdaDestination,
TMsvPartListaPartlist,
TRequestStatus &aCompletionStatus
)[pure virtual]

Creates a reply message to the current message context, and allows the user to edit it through a message-type specific editor.

Some MTMs may support inclusion of elements, specified by aPartlist, from the original message in the reply. The parent for the new entry is specified in aDestination. The returned CMsvOperation object completes when editing the reply is complete. On completion, the context is set to the reply message.

Requirements:

A typical implementation for this function would include the following steps:

1. create a new reply entry by calling CBaseMtm::ReplyL()

2. call EditL() allow the user to edit the reply

3. return a CMsvOperation-derived object to provide asynchronous control and monitoring of the operation

If message replies are not supported, implementations should leave with KErrNotSupported.

leave

KErrNotSupported The User Interface MTM does not support reply operations

leave

Other Dependent on implementation

If successful, this is an asynchronously completing reply operation. If failed, this is a completed operation, with status set to the relevant error code.

Parameters

TMsvId aDestinationThe entry to which to assign the reply
TMsvPartList aPartlistDefines the parts which are to be copied from the original message into the reply. See CBaseMtm::ReplyL() for details.
TRequestStatus & aCompletionStatusThe request status to be completed when the operation has finished

Session()

IMPORT_C CMsvSession &Session()const [protected]

SetPreferences(TUint)

IMPORT_C voidSetPreferences(TUintaFlags)

Parameters

TUint aFlags

Type()

IMPORT_C TUidType()const

UnDeleteFromL(const CMsvEntrySelection &, TRequestStatus &)

IMPORT_C CMsvOperation *UnDeleteFromL(const CMsvEntrySelection &aSelection,
TRequestStatus &aStatus
)[virtual]

Parameters

const CMsvEntrySelection & aSelection
TRequestStatus & aStatus

ViewL(TRequestStatus &)

CMsvOperation *ViewL(TRequestStatus &aStatus)[pure virtual]

Views an entry.

For message contexts, this usually launches the appropriate message viewer. Other context types leave with KErrNotSupported. The returned CMsvOperation object completes when viewing is complete.

Requirements:

Implementations should:

1. check aEntry.iType.iUid to ensure that they can view the requested type of entry and leave with code KErrNotSupported if they cannot

2. return a CMsvOperation-derived object to provide asynchronous control and monitoring of the operation

leave

KErrNotSupported The User Interface MTM does not support view operations, or viewing is inappropriate to the current context

leave

Other Dependent on implementation

If successful, this is an asynchronously completing view operation. If failed, this is a completed operation, with status set to the relevant error code.

Parameters

TRequestStatus & aStatusThe request status to be completed when the operation has finished

ViewL(TRequestStatus &, const CMsvEntrySelection &)

CMsvOperation *ViewL(TRequestStatus &aStatus,
const CMsvEntrySelection &aSelection
)[pure virtual]

Views a selection of entries.

For message contexts, this usually launches the appropriate message viewer. Other context types leave with KErrNotSupported. The returned CMsvOperation object completes when viewing is complete.

Requirements:

Implementations should:

1. check aEntry.iType.iUid to ensure that they can view the requested type of entry and leave with code KErrNotSupported if they cannot

2. return a CMsvOperation-derived object to provide asynchronous control and monitoring of the operation

leave

KErrNotSupported The User Interface MTM does not support view operations, or viewing is inappropriate to the current context

leave

Other Dependent on implementation

If successful, this is an asynchronously completing view operation. If failed, this is a completed operation, with status set to the relevant error code.

Parameters

TRequestStatus & aStatusThe request status to be completed when the operation has finished
const CMsvEntrySelection & aSelectionSelection of message entries

Member Enumerations Documentation

Enum anonymous

Progress information buffer length.

Enumerators

EProgressStringMaxLen = 255

Defines the maximum buffer length used in GetProgress() to hold progress information.

Member Data Documentation

CBaseMtm & iBaseMtm

CBaseMtm &iBaseMtm[protected]

The CBaseMtm-derived object (Client-side MTM) that requested the User Interface MTM. It is set by the constructor.

CCoeEnv * iCoeEnv

CCoeEnv *iCoeEnv[protected]

Control environment object. It is set by the constructor.

TAny * iExtensionData

TAny *iExtensionData[private]

TUint iFlags

TUint iFlags[protected]

This flag records the preferences as set by SetPreferences().

CRegisteredMtmDll & iRegisteredMtmDll

CRegisteredMtmDll &iRegisteredMtmDll[private]

TInt iResourceFileOffset

TInt iResourceFileOffset[private]
© Nokia 2010.