I think it would be very very useful if on copy / move / delete functions, Total Commander could put in a queue all the question it has to ask and try to do the tasks that it can actually do.

Usually these functions require supervision because TC always finds something to ask even if you set it to "skip all" ... I have been frustated a lot of times when I've asked it to do a huge task (copy or move the whole hard drive), went away and after I came back in several hours to find back that it has actually done 1% of the job just because it is wating for user input regarding a question like "whould you like to copy this file who has more than 255 characters" or "cannot copy some windows system file" etc ...

Support!!!
For example to collect such messages in a separate log window with the "ok" button.

Also propose to duplicate (eg tiny buttons with menus) on the window of the copy/rename -options "overwrite" "rename" etc. - often I forget to put them ahead of time and have to wait to the first issue to press "yes to all"..._________________I beg pardon for bad English.

I think it would be very very useful if on copy / move / delete functions, Total Commander could put in a queue all the question it has to ask and try to do the tasks that it can actually do.

Usually these functions require supervision because TC always finds something to ask even if you set it to "skip all" ... I have been frustated a lot of times when I've asked it to do a huge task (copy or move the whole hard drive), went away and after I came back in several hours to find back that it has actually done 1% of the job just because it is wating for user input regarding a question like "whould you like to copy this file who has more than 255 characters" or "cannot copy some windows system file" etc ...

Thanks.

Concerning filenames longer than 259 chars, you could add the following line to wincmd.ini in order to make TC always copy those files:

I have checked it now: You get this error when you try to delete a file with a very long name to Recycle bin. Currently the Recycle bin doesn't support such long names. TC doesn't delete the file directly to avoid possible data loss, but warns the user instead. Unfortunately there was no time to get a translation for a warning about recycle bin, so TC only warns about the length.

Try deleting the file with Shift+Del instead._________________Author of Total Commander
http://www.ghisler.com

also, just a note for you, my recycle bin was set to "delete without sending to recycle bin" when i didn't push shift-f8....

by the way, thanks for the responses. you are an awesome developer, to respond and follow up as you have done with all my questions. ever take vacations? or are you in front of a terminal all day like me? LOL

and, total commander is the program that makes windows "usable" because if i had to deal with explorer.exe as a "file manager" i would be writing this from an insane asylum.

I'm indeed looking for a solution for unattended copying. However, it's not that easy - for example, if a disk is removed or a network PC turned off, all operations would fail if there weren't a message to the user on the first._________________Author of Total Commander
http://www.ghisler.com

How about grouping the queue on destination? Before starting on such a group you could check the availability of the destination. If the destination is not available, just move on to the next group. It would be safe to assume that if the destination is not present because it is a removable (and removed) or network location (and off-line) it is no use to retry for every single file operation. A group single message after finishing the other queue group items would be enough to warn the user.
You might want to check the TeraCopy queue implementation for ideas. If some file operation cannot be executed (also for unreadable source files), it is skipped and logged. The user can afterwards 'clean up' all successful results and see all failures. After fixing the problem (e.g. network drive had a red cross but is being re-enabled) the remaining operations can be re-executed.

This may have been asked before, but I can't find it. Is there any way to disable the copy or move confirmation prompt? Preferences -> Misc allows you to disable overwrite and delete non-empty directory prompt - nowhere is simple copy and move mentioned anywhere. Any ideas?

I'm indeed looking for a solution for unattended copying. However, it's not that easy - for example, if a disk is removed or a network PC turned off, all operations would fail if there weren't a message to the user on the first.

Hi Christian, this is my first post here, but I've been using TC for years (I'm registered too!) -- and I sometimes stumble on to these forums and see the discussions on various issues -- but I really wanted to respond to this comment, so I went ahead and joined the forum. [I know the thread is a little old, but hopefully you'll see my response. ]

I want to point out that what you describe above is not the asked for feature. No operation should "fail", because you're still waiting for user feedback on those operations -- the point is: waiting for that feedback shouldn't block the rest of the batch operation. -- TC can (and should ) still ask whatever question it was going to ask.

For example: It's very frustrating when 3% of the files you want to copy have some random issue, and so the other 97% don't get copied, because TC stopped to ask a question. Why not ask the question without stopping. For some scenarios, like you mention, it won't make a lot of difference -- but -- it also doesn't make them any worse -- However, for many scenarios, like mine above (and the original feature requester's) it will make a night-and-day improvement.

If multiple items get added to that queue, because they need user feedback, that's fine. But there's no way it could "fail" an entire drive without user feedback -- it would only "skip" it, continue copying everything else (if there was anything else it could copy), while prompting for the feedback on those items in the waiting-for-feedback queue.

If all of the files had the same issue though, and you needed an answer (like in the scenario you mentioned), it wouldn't be any worse than what we have right now.

To illustrate, let's say you begin a massive copy operation, and TC hits a problem file, so, it needs to ask the user a question -- that question comes up on the screen (just like now -- or in a different UI -- doesn't matter) -- but the copy moves on to the next file and then continues the process for all of the files instead of waiting for user input.

Once the user answers the question, that file is moved back into the queue, as the next file to be processed with the option the user specified.

(Additionally, if they checked the "yes to all" checkbox, then any other file with the same question waiting to be answered shouldn't have to ask.)

"Sequential pop-ups" (i.e. question #2 doesn't pop-up until the user has answered question #1, etc.) is probably the easiest to implement. -- But you could do lots of other things too, like you could make the copy dialog box taller and show the queued prompt(s) below it (showing only one, or showing them all in a list, maybe grouping them by type, or maybe tabbing them, etc.) -- but honestly, again, sequential, non-modal, pop-ups are just fine with me.

Last edited by BrainSlugs83 on Wed Mar 12, 2014 9:18 pm; edited 1 time in total