[phkahler]

"Undo copy" seems like it should not even exist. Delete does the same. Seems like the result of trying to hard to "improve" the UI.

[bobbylarrybobby]

It makes sense if you accidentally paste somewhere to immediately be able to undo. But, just like in a text editor, undo should undo the most recent change. Once a copied file has edits, the copy operation isn't most recent, so that's not what should be undone. Of course, file explorer would need to be aware of changes to files it hadn't made for this to work.

[phkahler]

I hate to admit it, but this is a valid point. I've used the undo/redo stack in Windows when moving files around and it can be very useful. Consistency of the UI is something I value and often fault microsoft for not having ;-) So undo the copy but they need to get it right - can't undo once the file changed.

[Szpadel]

i guess simple check for file size and last modification would do the job

[phkahler]

>> i guess simple check for file size and last modification would do the job

Or instead of adding even more code, they could remove the feature and let the user Delete the copy.

[ElongatedMusket]

Except delete sends the file to the recycling bin, where it can easily be recovered. Undo copy removes the file from disk!

[jraph]

No, it makes sense. You might have copied something by mistake, undo is natural, and allows you to keep the undo/redo stack usable.

It just needs to be designed very carefully and not be actionable by mistake without confirmation.

[mmis1000]

It's actually easy to copy files by accident in windows. Although I think they should prompt the use about whether they want to copy the file rather then add a undo operation.