- This topic has 4 replies, 2 voices, and was last updated 7 hours, 27 minutes ago by
.
-
Posts
-
If a path is typed, for instance \\srv-share\c$\windows\temp, the application goes in the path then the application goes at the root of network. Then, the use of the back arrow permits to go to the entered path.
Moreover, the left tree does not reflect the network path browsed, it stays at the network root
For performance issues, I am not sure all accessed pathes should be kept in the tree, especially when the network path is no more accessible (destination computer powered off for example).
Hi HomeBoy,
The reason of the symptoms you described is that the Tree doesn’t show the hierarchy for ‘non-shell’ items like the \\ServerName\…
After your message and checking the reasons, I decided to proceed like File Explorer and thus, to ‘inject’ non-shell nodes until the shell takes over again.
Was needed for the \\ServerName\ and the for the root drive \c$\ or any other root. After that, the shell takes over again.
This is what it looks to on my Dev version:
I am not sure I got everything in your explanation, but thanks and great to know it will already part of new release and see that new release will come so early.
This answer raises one question, so far I have not tested it yet, but are you handling very long pathes and names? As far as I remember, you can do it by handling all pathes with specific syntax like \\?\C:\ for a drive letter (C:\ in this example) or \\?\UNC\server\share for a network drive (\\server\share in this example).
I am not sure how far it affects this thread specifically or the whole program in general.Hi HomeBoy,
I recently improved support for very long paths in FileVoyager. There may still be cases that are not handled properly, but in most situations this is due to limitations of Windows itself. File Explorer exhibits the same issues for the same reasons.
Regarding the specific case in this Topic, I tested using extremely long paths created for stress testing, and everything worked correctly.
The key point is that FileVoyager does not rely on plain text paths. Instead, it uses Item ID Lists (aka PIDLs), which are binary structures used by the Windows Shell to identify objects.
A PIDL represents a path as a sequence of linked identifiers rather than a single string. Because of this, it avoids many of the traditional MAX_PATH limitations associated with text-based paths. In practice, PIDLs allow handling much longer paths than standard string-based approaches.
- You must be logged in to reply to this topic.