I've always been a bit mystified by the order BC seems to scan directory trees. It seems to skip around a lot. Is there any explanation of this traversal order and any way to control it?
Since BC4 often craps out on me when doing very large directory compares, I would very much like to be able to traverse the directories in an order that makes it easier for me to restart it and omit those directories that were successfully completed on previous attempts. i.e. a strict depth-first pre-order traversal, based on the sort order of the current view (or let me independently specify a traversal sort order—name, size, modified date_time, etc., ascending or descending).
Finder copy operations are carried out in this order, making it easier to continue with the remaining files/folders after the Finder aborts a copy operation.
Since BC4 often craps out on me when doing very large directory compares, I would very much like to be able to traverse the directories in an order that makes it easier for me to restart it and omit those directories that were successfully completed on previous attempts. i.e. a strict depth-first pre-order traversal, based on the sort order of the current view (or let me independently specify a traversal sort order—name, size, modified date_time, etc., ascending or descending).
Finder copy operations are carried out in this order, making it easier to continue with the remaining files/folders after the Finder aborts a copy operation.
Comment