|  | Home · All Classes · Modules

# QAbstractFileEngineIterator Class Reference
[QtCore module]

The QAbstractFileEngineIterator class provides an iterator interface for custom file engines. More...

### Methods

- __init__ (self, QDir.Filters, QStringList)
- QFileInfo currentFileInfo (self)
- QString currentFileName (self)
- QString currentFilePath (self)
- QDir.Filters filters (self)
- bool hasNext (self)
- QStringList nameFilters (self)
- QString next (self)
- QString path (self)

## Detailed Description

The QAbstractFileEngineIterator class provides an iterator interface for custom file engines.

If all you want is to iterate over entries in a directory, see QDirIterator instead. This class is only for custom file engine authors.

QAbstractFileEngineIterator is a unidirectional single-use virtual iterator that plugs into QDirIterator, providing transparent proxy iteration for custom file engines.

You can subclass QAbstractFileEngineIterator to provide an iterator when writing your own file engine. To plug the iterator into your file system, you simply return an instance of this subclass from a reimplementation of QAbstractFileEngine.beginEntryList().

Example:

     QAbstractFileEngineIterator *
     CustomFileEngine.beginEntryList(QDir.Filters filters, const QStringList &filterNames)
     {
         return new CustomFileEngineIterator(filters, filterNames);
     }

QAbstractFileEngineIterator is associated with a path, name filters, and entry filters. The path is the directory that the iterator lists entries in. The name filters and entry filters are provided for file engines that can optimize directory listing at the iterator level (e.g., network file systems that need to minimize network traffic), but they can also be ignored by the iterator subclass; QAbstractFileEngineIterator already provides the required filtering logics in the matchesFilters() function. You can call dirName() to get the directory name, nameFilters() to get a stringlist of name filters, and filters() to get the entry filters.

The pure virual function hasNext() returns true if the current directory has at least one more entry (i.e., the directory name is valid and accessible, and we have not reached the end of the entry list), and false otherwise. Reimplement next() to seek to the next entry.

The pure virtual function currentFileName() returns the name of the current entry without advancing the iterator. The currentFilePath() function is provided for convenience; it returns the full path of the current entry.

Here is an example of how to implement an interator that returns each of three fixed entries in sequence.

     class CustomIterator : public QAbstractFileEngineIterator
     {
     public:
         CustomIterator(const QStringList &nameFilters, QDir.Filters filters)
             : QAbstractFileEngineIterator(nameFilters, filters), index(0)
         {
             // In a real iterator, these entries are fetched from the
             // file system based on the value of path().
             entries << "entry1" << "entry2" << "entry3";
         }

         bool hasNext() const
         {
             return index < entries.size() - 1;
         }

         QString next()
         {
            if (!hasNext())
                return QString();
            ++index;
            return currentFilePath();
         }

         QString currentFileName()
         {
             return entries.at(index);
         }

     private:
         QStringList entries;
         int index;
     };

Note: QAbstractFileEngineIterator does not deal with QDir.IteratorFlags; it simply returns entries for a single directory.

See also QDirIterator.

## Method Documentation

### QAbstractFileEngineIterator.__init__ (self, QDir.Filters, QStringList)

Constructs a QAbstractFileEngineIterator, using the entry filters filters, and wildcard name filters nameFilters.

### QFileInfo QAbstractFileEngineIterator.currentFileInfo (self)

The virtual function returns a QFileInfo for the current directory entry. This function is provided for convenience. It can also be slightly faster that creating a QFileInfo object yourself, as the object returned by this function might contain cached information that QFileInfo otherwise would have to access through the file engine.

See also currentFileName().

### QString QAbstractFileEngineIterator.currentFileName (self)

This method is abstract and should be reimplemented in any sub-class.

This pure virtual function returns the name of the current directory entry, excluding the path.

See also currentFilePath().

### QString QAbstractFileEngineIterator.currentFilePath (self)

Returns the path to the current directory entry. It's the same as prepending path() to the return value of currentFileName().

See also currentFileName().

### QDir.Filters QAbstractFileEngineIterator.filters (self)

Returns the entry filters for this iterator.

See also QDir.filter(), nameFilters(), and path().

### bool QAbstractFileEngineIterator.hasNext (self)

This method is abstract and should be reimplemented in any sub-class.

This pure virtual function returns true if there is at least one more entry in the current directory (i.e., the iterator path is valid and accessible, and the iterator has not reached the end of the entry list).

See also QDirIterator.hasNext().

### QStringList QAbstractFileEngineIterator.nameFilters (self)

Returns the name filters for this iterator.

See also QDir.nameFilters(), filters(), and path().

### QString QAbstractFileEngineIterator.next (self)

This method is abstract and should be reimplemented in any sub-class.

This pure virtual function advances the iterator to the next directory entry, and returns the file path to the current entry.

This function can optionally make use of nameFilters() and filters() to optimize its performance.

Reimplement this function in a subclass to advance the iterator.

See also QDirIterator.next().

### QString QAbstractFileEngineIterator.path (self)