Internally Qt uses / as path separator, but all path taking APIs accept both / and \, so you can just always use / (which is easier because you don't have to escape it).
If you need to pass the path to some native platform API or display it to the user in a platform correct form you can use QDir::toNativeSeparators, which will convert all the separators to current platform appropriate.
It's usually not needed, but if you insist on building the platform correct path yourself you can use QDir::separator().

So both of those will do the same:

QString path1 = QDir::toNativeSeparators("\\this/is\\my/fancy\\path"); QChar sep = QDir::separator(); QString path2 = sep + "this" + sep + "is" + sep + "my" + sep + "fancy" + sep + "path".

@SimonSchroeder
QDir is only for directories, not for files. So it is not a (suitable) candidate for general "file paths".

@lemons just run into problems to send files in one of my customer apps with API 30 and Android 13 devices.
did your changes here and all works as expected.
will update my share example app.
THX

@EchoReaper said in How to create a new QDir from an existing QDir + a subfolder?:

Normally, scripting languages will you allow to do something like QDir folderInput = input / "SubfolderName", but Qt doesn't. I could just use what I have above, but I'm not a fan of it because it hardcodes the slash. I could do input.path() + QDir::separator() + "SubfolderName", but that's too verbose. Does Qt have a more desirable way to index a subfolder of an existing QDir?

I would say the "correct" Qt way of producing the path to a sub-folder, without using / or QDir::separator() the way you have (which isn't great if your starting directory ends with a /, like / or C:/, e.g. when QDir::isRoot() == true), is to use https://doc.qt.io/qt-5/qfileinfo.html#setFile-2, void QFileInfo::setFile(const QDir &dir, const QString &file).

You/Qt don't know whether the sub-item is a file or directory, that's why it's a QFileInfo method rather than a QDir one. You can then, say, feed QFileInfo::absoluteFilePath() to a new QDir() if you want to access it as a directory.

If you actually wish to create the sub-directory you could use https://doc.qt.io/qt-5/qdir.html#mkdir or https://doc.qt.io/qt-5/qdir.html#mkpath.

I am using Qt 5.10.1, on CentOS 7

@Maarten-Verhage said in Does QDir impose a maximum path limit on Windows?:

When the path is prepended with "\?". Does Qt call the winapi functions with this prepend?

Yes, here and here.

But I think I still have the responsibility not to exceed the number of 32,767 for Qt development on Windows, right?

As far as I can see in the source, yes, you do.

@panosk
Thanks it works :)

Henrik

@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.

Is QCollator::compare a good option for this? I mean, I simply implement a sorting algorithm based on the result from QCollator::compare. Usually the number of files will be limited to ~3000.

did you figure out how to make this program work? if so, please provide details on it because I am trying to do the same thing with a current project.

Hi,

Did you check the permissions of this file ?

Are you running Windows 8 ?

I've tested on windows. It seems the only possible solution is to ignore native dialog.

QFileDialog dialog; dialog.setFileMode(QFileDialog::DirectoryOnly); dialog.setOption(QFileDialog::DontUseNativeDialog, true); dialog.setOption(QFileDialog::ShowDirsOnly, false); dialog.exec(); qDebug() << dialog.directory();

@GrahamL said:

QDir::mkpath

this is the implantation
So My best guess is sadly no since the actual mkdir
lives in QDirPrivate.

bool QDir::mkpath(const QString &dirPath) const { const QDirPrivate* d = d_ptr.constData(); if (dirPath.isEmpty()) { qWarning("QDir::mkpath: Empty or null file name(s)"); return false; } QString fn = filePath(dirPath); if (d->fileEngine.isNull()) return QFileSystemEngine::createDirectory(QFileSystemEntry(fn), true); return d->fileEngine->mkdir(fn, true); }

Ahh Ok

Thanks

You can check your directory by doing:

qDebug() << dir.absolutePath(); dir.cdUp(); qDebug() << dir.absolutePath();

That should tell you what's happening and why. I have used QDir specifically to navigate inside bundles on Mavericks and it worked so check what those values are and it might show you the problem.

Brilliant thanks!