ghisler(Author) wrote: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.