0 |
This panic is raised by:
the TDriveUnit(TInt
aDrive) variant of the TDriveUnit constructor,
the (TInt aDrive) variant
of the TDriveUnit assignment operator
when the specified drive number is greater than or equal to KMaxDrives,
i.e. 26. |
1 |
This panic is raised by:
the TDriveUnit(const
TDesC& aDriveText) variant of the TDriveUnit constructor,
the (const TDesC&
aDriveText) variant of the TDriveUnit assignment
operator
when the specified drive letter is invalid, i.e. does not correspond
to a drive number. |
2 |
This panic is raised when searching for the next file using TFindFile::Find() or TFindFile::FindWild() before the initial call specifying the search method. Calls to TFindFile::Find() cannot
be made until an initial call has been made to either of: Calls to TFindFile::FindWild() cannot be made
until an initial call has been made to either of: |
3 |
Not used. |
4 |
Not used. |
5 |
This panic is raised by a call to TFileText::Seek() when
the seek mode passed to the function is neither TSeek::ESeekStart() nor TSeek::ESeekEnd(). |
6 |
Not used. |
7 |
Not used. |
8 |
Not used. |
9 |
Not used. |
10 |
This panic is raised by the CFileMan implementation
when the operation to be run is undefined. |
11 |
This panic is raised by CFileBase::CurrentEntry() if
there is no current entry. |
12 |
The value returned by the file management observer functions: is not a valid MFileManObserver::TControl() enum
value. |
13 |
Not used. |
14 |
Not used. |
15 |
This panic is raised in debug builds only. This
panic is raised in a call to CDirScan::SetScanDataL() when
the path does not contain at least one '\' character. |
16 |
Not used. |
17 |
This panic is raised by RFile::Lock() when the
number of bytes defining the region to be locked is either zero or negative. |
18 |
This panic is raised by RFile::UnLock() when
the number of bytes defining the region to be unlocked is either zero or negative. |
19 |
All variants of the RFile::Read() and RFile::Write() functions
take an argument denoting an offset value, in bytes, from the start of a file;
the panic is raised by these functions when the offset value is negative. |
20 |
This panic is raised by RFile::SetSize() when
the argument denoting the size of the new file is negative. |
21 |
This panic is raised by RFile::SetAtt() and RFile::Set() when
the same attribute bit is set in both the bitmask that indicates the file
attributes to be set and the bitmask that indicates the attributes to be cleared. |
22 |
The panic is raised by the [] operator of TEntryArray,
when the index value passed to the operator is greater than or equal to the
number of elements in the array. |
23 |
This panic is raised by CDir::Sort() when the
method of sorting, as defined by the single function argument, is none of
the entries:
TEntryKey::ESortNone()
TEntryKey::ESortByDate()
TEntryKey::ESortBySize()
TEntryKey::ESortByExt()
TEntryKey::ESortByUid()
TEntryKey::ESortByName()
|
24 |
This panic is raised by the TParsePtr constructor
that takes a reference to a filename, when the name cannot be parsed. |
25 |
This panic is raised by the TParsePtrC constructor
that takes a const reference to a filename, when the name cannot be parsed. |
26 |
This panic is raised by RFs::ReadFileSection() when
the specified number of bytes to be read from the file is greater than the
maximum length of the target descriptor. |
27 |
This panic is raised in debug builds only. This
panic is raised by the RFile::Write(const TDesC8&,TInt) variant
when the specified length is greater than the length of the source descriptor. |