Undo History : Cancelled ops

[meteorquake]

I notice that in the Undo history it also includes as Moves, items I moved in and cancelled because they would have overwritten an existing file.
It's useful to know they were cancelled but this I would think becomes a bug in that it offers an Undo for it when no action was in fact taken. Clicking the Undo would if clicked I presume move the pre-existing file.
I'm not sure if this is a trivial thing to correct. If it is it's worth doing, I often use the Undo History to review my actions to make sure I didn't mis-move or mis-delete anything. If it's not trivial it's not high priority. I presume it would be much easier to fix this when you implement a native move/copy rather than trying to work out what the system move/copy carried out, although these were a drag from Explorer into Everything, which I suppose might require seeing if the target files actually changed.
d

[void]

The Windows shell handles the drop.

Everything receives no information on the file operations performed.
Everything only knows the intended operation (move / copy / create shortcut).



Please try the Index Journal to view the performed file operations.
Moves and renames can be undone here.