Hope someone can point me in the right direction, I am trying to find out if it is possible to select multiple auto collections and save them to different folders based on the auto collection name?
e.g. Auto collections are:
Auto-Collection-01
Auto-Collection-02
Auto-Collection-03
If I select them all and download them it saves them all into one folder (I think it is the first auto collection I choose, could be the last not too sure now…) so all files are saved under the folder name "Auto-Collection-01"
If I select them individually then it is saved into individual folder names as per the 3 collections i.e. files in 3 folders "Auto-Collection-01" to 03 respectively.
I did do a search and found some posts going back to 2003 – but hoped that it would have been added as a feature and perhaps I just cannot find it…
Also does anyone know what is the folder/path limit to the auto save folder structure please? It seems to vary and the longest from the root of the drive I seem to get is about 100 characters (including spaces and backslashes) + the file name (normally about 7+3) so in total about 110 characters. I am using the root of the drive just to eliminate any windows path length and also NTFS file system.
Auto Collections – multiple select and save and path length
Re: Auto Collections – multiple select and save and path len
Unless it is autosave the program suggests a folder.
If auto save, sometimes par2 and rar files are in different collections, if they are saved into different folders, then unpack won't work since it only looks into the same folder.
So the question how it could be implemented (what logic).
As to the path length, there is a constant somewhere in the code, when a folder is created, the file path length is not known, so it is some conservative number, because of the windows small maximum path length. I could check maybe the constant could be set explicitly in properties, so users could change it.
If auto save, sometimes par2 and rar files are in different collections, if they are saved into different folders, then unpack won't work since it only looks into the same folder.
So the question how it could be implemented (what logic).
As to the path length, there is a constant somewhere in the code, when a folder is created, the file path length is not known, so it is some conservative number, because of the windows small maximum path length. I could check maybe the constant could be set explicitly in properties, so users could change it.