XYplorer Beta Club

I have the following problem:
I have large files located in different directories that I want to copy/move to other directory/directories.
Today, i have to copy/move the files in the following sequencial manner:
1a) Goto Dir1
1b) copy/cut file1
1c) Goto Dir2
1d) Paste file1
1e) WAIT UNTIL THE TRANSFER IS FINISHED

2a) Goto Dir3
2b) copy/cut file2
2c) Goto Dir4
2d) Paste file2
2e) WAIT UNTIL THE TRANSFER IS FINISHED

etc...

I think you understand the frustration of waiting for each transfer to be finished to proceed to the next copy/move.

Create in XYplorer function that lists pending copy/move until the user press a [proceed] button.
The list should present the source path/file, target path/file, copy/move type, overwriting/renaming option.
When the user press [proceed], the list is processed by XYplorer and the user can do something else instead of sitting and watching stupidly the copy/move progress bar
It could be useful to save the lists to use the feature like a backup tool
Adding items to the list could be done by using the shortcut Ctrl+Alt+V in the target directory

noutters wrote: Create in XYplorer function that lists pending copy/move until the user press a [proceed] button. ...
It could be useful to save the lists to use the feature like a backup tool
Adding items to the list could be done by using the shortcut Ctrl+Alt+V in the target directory

Definitely a good idea. I had something similar in a previous version (v3.50.0074 - 24.06.04 19:52) but removed it because it was not well thought out. The idea is still good though! (see also "copy queue" http://www.xyplorer.com/forum/viewtopic.php?t=521)

Ctrl+Alt+V: yes, brilliant! ...

Uhhh, did I mention that I lack time currently? This feature cannot be done in a few minutes... Please keep it warm and remind me later...

I am glad to see such a positive response. I did not expect this feature to be coded in a short time. As you wrote, I am sure you are swamped in a lot of programming on other fronts.

admin wrote:Uhhh, did I mention that I lack time currently? This feature cannot be done in a few minutes... Please keep it warm and remind me later...

Well I hope that after almost 3 & 1/2 years this feature hasn't cooled down yet and recently I had more and more need for it. I have video files sorted into different directories and I want to pick and choose a few from various folders to put onto an external hard drive to take to a friend of mine. If I was to visit each directory and DnD the files I need I might as well use WE and I probably should given how XY isn't on best terms with Vista SP1 in terms of copying files. However, having a list that I can add things to and then hit a key and all those files will jog down a yellow-brick road onto the HDD will be a blessing. It will certainly give me an excuse to enjoy [insert name of your favourite beverage here] while XY is hard at work. As far as I know, there is no equivalent/similar feature in other file managers so here's your chance to jump on the bandwagon of trademarking a name and rewrite file management history

I'm not sure this is exactly what you're after, but you might wanna check out this little script, allows you to create a "collection" of items, and later on move/copy/delete all collected items at once.

And if you want to add selected items to the active collection with one KS only, just assign it to a script such as

If that script creates a list of files, as I suspect it does, it might be the basis of a combine files script. Does it have the command-line limit problem?? If so, then it's no good to me since that is what I keep coming up against whenever I try to create a combine files routine - T.C. overcomes this and so far I've never reached a maximum number of files.

Gandolf wrote:If that script creates a list of files, as I suspect it does, it might be the basis of a combine files script. Does it have the command-line limit problem?? If so, then it's no good to me since that is what I keep coming up against whenever I try to create a combine files routine - T.C. overcomes this and so far I've never reached a maximum number of files.

hmm... what command-line limit? There is no command line used in that script, collections (list of items) are saved inside in INI file, and then processed (copy/move/etc) within XY.

So I think any limit would come from the INI file stuff, and that means a collection should be up to 32 766 characters for items' path/names (and separators). So there is a limit, but I'm not sure how many items you can store within a collection (and that would also depend on the length of the path they're in).

Of course, it could be rewritten not to use INI files, and using readfile/writefile directly. In such a case there's no more limit (well, might depend on available memory ). I don't have time to look into this right now, but that shouldn't be too hard to do I would imagine - if you're familiar with XY scripting that is. (Although user functions would be a nice help )

jacky wrote:I'm not sure this is exactly what you're after...

Close, though I would have preferred a more graphical way of doing things. I'm sure it will come with time. For now I would stick to Windows Explorer for my large copying needs. XY's own file copying/moving operations couldn't come here soon enough

jacky wrote:... what command-line limit? There is no command line used in that script, collections (list of items) are saved inside in INI file, and then processed (copy/move/etc) within XY.

So I think any limit would come from the INI file stuff, and that means a collection should be up to 32 766 characters for items' path/names (and separators)...

Something is not happy.

If I only have a few files with long paths, or many with short paths, then "CollectItems.ini" is created.

A large number of files with long paths (200+ characters, 150+ files), which is my usual situation, then no "CollectItems.ini" file is created and XY exits without saving any settings; and with no error message of any sort. The 32,766 limit has been exceeded I expect.

Oh well, some day I might have the time to look at scripting, but at the moment I'm up to my eyes in assembler.

This sounds like a great idea, but I sometimes have a need to copy a single file to multiple directories.
This could possibly be done as copy to: (list of directories) go.