8

Imagine: You are copying files from remote share/ftp/etc and connection is not very stable - from time to time you are receiving error messages "Source file cannot be read" or something like. If you are copying a few files, it's ok - just click appropriate button and wait for the next error. But if your files are big, or there is a lot if it you may decide to start transfer and go to sleep for some time. And what if in the very beginning of the process such error is happened? All time you was waiting is spoiled - files was not copied!
The idea: While copying/moving files, don't stop transfer if non-critical errors happened - just make a list of "problem" files with short diagnostic message(can't read,can't write, etc) and give an option to retry/fix issue as soon as user can do it.

P.S.: Sorry for my bad English.

Or, more simple Just add a check box "Always ignore".
What do you think of that ?

(It can be here, I never test)

florentg

I think that "Always ignore" isn't a good solution, if you want all requested files to be copied.

Your idea is great. I didn't take the importance of what you proposed.

But I am sure both are complementary/ Your system can be very hard to implement, especially for network drive but if it works, it would be great

Thanks, florentg! It's great, that not only me want this to be in KDE

As for implementation, I'm actually don't know, how things are done now, so introducing this feature may be hard or not.

I think that has been a GSOC project and so hopefully will be in KDE 4.8