Alt

_Just for clarification, I have enabled "NTFS long paths policy"._ https://superuser.com/a/1119980/1034786 --- > Probably uses some winapi incantations to convert from 8.3 short names. In the title it displays the...

Wait, but Qt works fine with long paths, I have checked it right now. Did I miss something? ```c++ #include #include #include // ... QString pathStr = "C:/[example-folder-0] images with...

> When I try to open a file in other hard drive: > > * `M:\[0]` > > I got the error: `Could not open path: \\?\M:\[0]\1.png` ("\\\\?\\" is [verbatim](https://docs.microsoft.com/windows/win32/fileio/naming-a-file?redirectedfrom=MSDN#win32-file-namespaces))....

Hm, there is an interesting moment. I have bash script that prints input file path (I just drag'n'drop it on the scripts): ```bash #!/bin/bash # Input file echo "$1" echo...

I have reinstalled Qt to recheck that long path. Yes, it works fine too. Both ```c++ QString pathStr = "M:/[example-folder-0]... ``` and ```c++ QString pathStr = "\\\\?\\M:\\[example-folder-0] ... ``` It's...

**Wait, maybe the problem reason is the old Qt?** You use Qt **5.12.14** (Prog version is 0.9.1) Here is the program's code: https://github.com/easymodo/qimgv/blob/a1058effeb341dfccab549a53c1e0be7c2c03415/qimgv/core.cpp#L813-L828 It works fine with the latest **Qt...

Yes, it's Qt version's problem. I have installed [Qt 5.2.1](https://www.qt.io/blog/2014/02/05/qt-5-2-1-released). Now I get the error when I'm trying to open a long path.  There was no problem with Qt...

Please, note, there are **two types** of problems: - with **long paths** `"\\\\?\\M:\\[example-folder-0] images with long path 2020.02.20\\";` - with **short paths** `"C:\\Users\\Username\\Downloads\\_EXAMP~1.20\\_SUBFO~2\\_SUBFO~1\\"` Files with long paths currently do no...

By the way, you have added Qt6 https://github.com/easymodo/qimgv/commit/d0fe882cf5b763a22962106ae2b00d416dd8d2e7 I can't check it, since it's difficult to build it for me, and the last alpha build was posted before this commit....

Well, with 1.0.2 no any problem is resolved. But not it does not display the floated warning `Could not open path: \\?\D:\...`