Undo Move to become copy

[mwb1100]

Now that XY has Undo, I'd like to ask for an additional feature to it - one that starts entering "Do what I meant" command territory. One common mistake I make when draggin' and droppin' files is that I mean to copy files but end up moving them because the source happens to be on the same volume as the destination (does anyone else hate that modal behavior of drag-n-drop in Windows?). This isn't a disaster because nothing's lost (though I guess I might start modifying the moved files in the belief that there are safe copies elsewhere).

But now that there's an action log, it would be nice to have an option/command/mouse action/button (whatever) to XY that tells it, "I meant for this move to be a copy - turn that move action into a copy". I know that it seems like no big deal to simply copy the files back to where they were moved from, and it's not. But if you're like me, when you're faced with this situation, the initial reaction is a minor bit of panic (oh no! where the hell did those files go?) followed by a flustered clearing of the brain of whatever thing you were working on to a state where you're figuring out the fix (even if the fix is pretty simple and straightforward).

Having XY take care of those details would let me keep my mind on what I was working on rather than shift gears. It would just be a nice little add on feature to the super fantastic undo feature.

[admin]

I see your point but I hesitate because it would it would complicate an interface which is still pretty and clean.

Let's see what other ideas come up for Undo 2.0... (I have already a sheetful of them).

[PeterH]

A new undo-option named "undo move by simulating a copy" - ouh

And this never happens to me.
As I always copy/move with right mouse button, and always select the correct option.
This says: the idea of "distinguishing copy and move be comparison of source and destination drive" doesn't seem to be very intuitive.

[mwb1100]

I see your point but I hesitate because it would it would complicate an interface which is still pretty and clean.

And I see your point. Maybe there's a way to script this?

A new undo-option named "undo move by simulating a copy" - ouh

Yeah - I'd probably call it "redo move as copy", but I agree that it's probably not something everyone wants cluttering up a UI with.

This says: the idea of "distinguishing copy and move be comparison of source and destination drive" doesn't seem to be very intuitive.

I don't like it anyway. To me, whether I want a copy or a move is purely a function of my intent, not a function of how the source and destination might be related. But this is a Windows UI convention and an old one, so we're stuck with it. Maybe there's a tweak to change it, but I find that Windows tweaks (not so much tweaks to applications) are not particularly effective for me because I seem to always have to fight to keep them in line for some reason (regularly using 4 different machines, some of which are mainly used by other people is part of the reason, I think). Then I'd be left with having the additional variable of knowing how the machine I'm on is configured. Better for me to just leave things as they are and live with having to fix up my unintended moves.

I agree that getting into the habit of always using right-click-drag and select the operation is a good way to handle this. And I do often do that, but I think that left-click-drag is just too much of a habit for me to be able to go with the more controlled way 100% of the time.

I certainly think it would be very unwise for XY (or other applications) to behave differently than the Windows default, so I don''t want anyone to think that I'm even glancing down that path.

[PeterH]

You are very right with what you say - especially that XY should (and can) not change this behavior!
I was just too lazy to write all this...

Thanks to Bill God (or how is his name) I never could remember when it will copy or move - and so from that beginning I used right mouse dragging