binar wrote:
SkyFrontier, thanks for the code. Can you please also post some brief steps on how I'm suppose to use your script within xyplorer?
Sure.
1. Copy (CTRL+C) the entire code into clipboard;
2. Paste it (CTRL+V) into the Scripting > Run Script... dialog and press OK;
3. Everything else will be guided by the script itself, which will prompt you for each source individually or a whole list on a further dialog. So it's useful to get a base list at hand when you are about to start using the script.
In my understanding, you are asking for an easy way to select multiple source folders on multiple drives so they are parsed into a single copy operation, so this is what my script aims to deliver: first, a one-after-each-other dialog asking for individual folders, which can be feed one at a time but anywhere on multiple disks/locations; then, it pops a confirm box in which you can check the initial choices plus feeding a list of several other folders (assuming some of those sources can be listed on a pane, ie, they share a same parent folder, so it's easy for you to press ctrl+p to gather them at once - or edit them any other way).
http://www.xyplorer.com/xyfc/viewtopic.php?f=3&t=9595 mentions a concept (Virtual Folder) which I tried to imitate to help another user - it's a mess, as I thought I had mastered FindTemplates ini files but after some upgrades my scripts on this went broken for some reasons I had no time to investigate yet (partially because some functions were forced to work as commands only, recently).
The script is full of error check and some smartness but let me know what you find about it - usability sux, I'm aware, but it's the best I could do. As always, opened to suggestions.
But then you may want to go anywhere and queue your file ops yourself (which seems NOT to be what you want, per OP), so...
quoting Help on
Queue file operations
Check to process background file operations sequentially, in a queue, where successive operations are lined up in sequence and completed one after the other. If unchecked then background file operations are processed in parallel.
E.g. if you initiate a job, say a Copy operation, while another one is still in progress, the new one will be delayed until the other one is finished. One job is triggered after the next, until all pending jobs are completed. A copy queue, also known as asynchronous copy, avoids inefficient pseudo-parallel processing and undue stress on your HD head.
Notes
· This option is applied on a per-job basis in the moment the jobs are initiated by the user, so while one or more jobs are running in the background you can change the setting of "Queue file operations" to control how the next job is handled; running or pending jobs are not affected.
· There's no explicit limit applied to the number of parallel processes.
· Move operations within volume boundaries (see above Note on Move operations) are always processed in parallel (= not queued) regardless of the setting of Queue file operations, because they are usually fast and you rather expect immediate action.
· There is also a toolbar button for this setting.
...are you aware that there's a 'Enable BG Processing' and a 'Queue File Ops' couple of toolbar buttons, right? Right clicking them can bring you some options, either.