Page 1 of 1

long file name support in searches

Posted: 13 Apr 2014, 20:16
by rollhigh
Hi Jan

please see below:
as1.PNG
as1.PNG (25.56 KiB) Viewed 2862 times
as2.PNG
as2.PNG (53 KiB) Viewed 2862 times
Characters in one of the affected paths was approx 270 (including the file name).

actual file name is 100 characters.


AS 3.0 final version 64bit

Thanks

Re: long file name support in searches

Posted: 13 Apr 2014, 20:34
by Jan Rysavy
AS 3.0 doesn't support such long paths because there are several problems with Win32 API and such paths are simply not supported enough. Rename / simplify your directory structure.

Re: long file name support in searches

Posted: 13 Apr 2014, 21:31
by therube
enough
Enough, being that the API's are trash?
Or enough, that "people" don't typically use such long paths?

Because I certainly run into long path issues "enough" ;-).
(Though not from searches as I typically use Everything for searching. But certainly when attempting to access, move files. Suppose most typical reasons for me for such long paths are from extracting archives that are that way, or from saving files, when I may have my download manager set to recreate directory structure locally when saving files.)

Naming Files, Paths, and Namespaces

Re: long file name support in searches

Posted: 14 Apr 2014, 08:41
by Petr Solin
We have thought about adding support for extended-length paths (maximum total path length of 32,767 characters) some time ago. All these paths must be prefixed with "\\?\" when passing to Windows API. But we have found out that most of applications and also Windows API calls does not support it, so we have decide not to support it too. I think that neither Windows Explorer support these paths. Maybe we should add some support for them to allow shortening of such paths which is the only reasonable thing to do with them if you don't want to run into troubles.

Re: long file name support in searches

Posted: 14 Apr 2014, 23:44
by SelfMan
Peter you have my +1 from my side