In the "File" menu of the TreeSize main module there is now a menu item that allows to load the paths to scan from a text file. Feel free to comment on the new feature here.
any update on this? I need to be able to create a scan task using a text file generated regularly from one of our service lines and create a top level folder size report based on that list of folders.
I prefer to use the GUI and typically have a list of folders to scan (with multithreading) where each folder is in a different parent folder. Plus I cannot scan at the path of those parent folders due to time constraints as they contain thousands of other large folders many of which I don't need to scan.
Are those paths fix? Or do they change for each usage?
You can drop folders from Explorer to the TreeSize directory tree to let them scan. Is this helpful for you?
Activity Newest / Oldest
Team UltraSearch
In the "File" menu of the TreeSize main module there is now a menu item that allows to load the paths to scan from a text file. Feel free to comment on the new feature here.
Team UltraSearch
Status changed to: Released
Endre Endi
Yey, it's in progress.
Team UltraSearch
Status changed to: In progress
Team TreeSize
We will most likely add a new menu item "Select path list for scan" to the File menu.
drew calhoun, HPW
any update on this? I need to be able to create a scan task using a text file generated regularly from one of our service lines and create a top level folder size report based on that list of folders.
Team TreeSize
Other feature requests did receive more votes, which is why we implemented them first.
Please keep in mind that you can already scan such a file using the /SCAN command line parameter.
Team TreeSize
Status changed to: Open
Team TreeSize
Status changed to: Under review
Team TreeSize
You can already scan paths from a file using the /SCAN command line parameter followed by the file path. Is this sufficient for you?
I prefer to use the GUI and typically have a list of folders to scan (with multithreading) where each folder is in a different parent folder. Plus I cannot scan at the path of those parent folders due to time constraints as they contain thousands of other large folders many of which I don't need to scan.
Team TreeSize
Are those paths fix? Or do they change for each usage?
You can drop folders from Explorer to the TreeSize directory tree to let them scan. Is this helpful for you?
Using a combination of the drag-drop and the /scan methods, that should be good enough for now thanks.