What's the benefit of FileSystemModel::getFileInfo()? I would guess your this pointer is a nullptr

@JonB said in Best approach to create "virtual QFileSystemModel"?: Quite possibly. Though QFileSystemModel itself is sub-classsable alternatively. I don't see how subclassing QFileSystemModel will let me insert virtual nodes at the top of the tree and have other QFileSystemModels as branches lower in the tree. Thanks for the pointer to the example. I'll study it some more, but so far it's still eluding me how to manage the top of the tree but delegate things back to the QFileSystemModels lower in the tree. I'm trying to create a VirtualFileSystemNode that can hold a pathname or a QFileSystem model as its data, but no success yet.

@mahesh_j said in File Browser with context menu to unzip files: But I don't know what actions to add to the QMenu The actions you need. You have to create such a pop-up menu. Take a look at http://quazip.sourceforge.net/

breaks SOLID It doesn't. In fact, if it worked as you expected it would break SOLID it's definitely a serious design flaw Sorry to be brutal: No, it's not a flaw, you just didn't understand the design of model/views. To help you get a better idea of what is going on, try use the same model with 2 different treeviews. In only one of the view call setRootIndex, and then trigger the filtering.

Ok I found what was causing this awful bug. When I check if the map contains the index, I actually check the raw index not the QPersistantModelIndex so this is not the same object and I think qmap does not check equality using == operator . So I have to iterate over the map and check using QPersistantModelIndex "==" operators which can compare from a QModelIndex.

Hi, Apply the same filter you are using for your single folder version except that this time rather than using a QString you should keep a QStringList of the folders you want to show and use that.

That wasn't really clear from your original description. In that case, use a filter. QSortFilterProxyModel for example

I had issues making these solutions work for the QML TreeView. I ended up setting the root path of my QFileSystemModel to the directory I wanted to view. Then I set the rootIndex in the TreeView to the parent of the index for that directory. This is of course showed its siblings. Then I did the following to filter those siblings away. I also made this optional through a property as there are times when I want that behavior: bool filterAcceptsRow(int source_row, const QModelIndex &source_parent) const { FileSystemModel* tmodel = qobject_cast<FileSystemModel*>(parent()); if(tmodel){ QModelIndex index = tmodel->index(source_row, 0, source_parent); QModelIndex rootIndex = tmodel->index(tmodel->rootPath()); if(!rootIndex.isValid() || !index.isValid()) return false; return ((index == rootIndex) || !(tmodel->filtersiblings() && isSiblingOf(index, rootIndex))); } return false; } bool isSiblingOf(const QModelIndex& index, const QModelIndex& parent) const { if(!index.isValid() || !parent.isValid()) return false; QModelIndex sibling; int row=0; do{ sibling = parent.sibling(row,0); if(sibling == index) return true; ++row; }while(sibling.isValid()); return false; } I took more of a blacklist approach versus a whitelist approach.

@tokafr Super. so it can copy files on its own ? Doc hinted it, but I was not sure.

@tokafr Oh. That would have been too easy then :) http://stackoverflow.com/questions/11050977/removing-a-non-empty-folder-in-qt has a function that looks good. bool removeDir(const QString & dirName) make sure to give it full path. I dont think QFileSystemModel can do it directly . Not that i have seen.

That I understood. That's why I think that QDirIterator is a better tool to find what you want on your drive.

Thanks everybody

You're welcome ! By the way, now you can use the "Topic Tool" button to mark the thread as solved, it keeps the things cleaner :)

Brilliant thanks!

@Chris-Kawa I am building from within Qt Creator (Windows 7), my .pro file didn't contain that! it just had: QT += gui Thank you Chris.