Look up the panic in the SDK docs in future. For now, the panic is described as:
This panic is raised by any operation which accesses an element of an array by explicit reference to an index number, for example, the Delete(), InsertL() and At() member functions or the operator Operator[]. It is caused by specifying an index value which is either negative or is greater than or equal to the number of objects currently within the array.
Also, why go such a long winded way to invoking operator[]? The following will probably be better:
Forum posts: 10
Look up the panic in the SDK docs in future. For now, the panic is described as:
This panic is raised by any operation which accesses an element of an array by explicit reference to an index number, for example, the Delete(), InsertL() and At() member functions or the operator Operator[]. It is caused by specifying an index value which is either negative or is greater than or equal to the number of objects currently within the array.
Also, why go such a long winded way to invoking operator[]? The following will probably be better:
const TDesC& CRFsEngine::FindFileName(TInt aFileNameIndex){
if (aFileNameIndex >= 0 && aFileNameIndex < iFileList->Count())
{
return (*iFileList)[aFileNameIndex].iName;
}
return KNullDesC;
}
Forum posts: 15
actually the problem was with the CurrentItemIndex() function i used.
insted i used MdcaPoint() n it worked alrite.
neways thanks for the help.
Punit.