I'm not really sure if this is actually a bug, in this example it would be useful but I would not expect (and in some cases want) to let FDT modify files when copying it. I'll change that ticket to an improvement to check out by the project owner.

Philipp Arnolds added a comment - 22/Mar/12 02:39 PM I'm not really sure if this is actually a bug, in this example it would be useful but I would not expect (and in some cases want) to let FDT modify files when copying it. I'll change that ticket to an improvement to check out by the project owner.

I'm going to vote against this; however, if more customers vote on it we can reconsider.

Here is what is going on :

Copy and paste does exactly that - it copies a file, exactly, then creates a duplicate of it somewhere else. If we add a refactor step to it - then it's no longer copy / paste. Everyone knows what copy / paste is and expects that. We would be changing what people expect.

I propose a different option, currently we have 'Move...' and move Refacotring - which are similar to what is described in this ticket. We can just add a key binding to similar to "Move ..." called 'Paste and Refactor'.

Alan K (Deprecated) added a comment - 03/May/12 05:06 PM - edited I'm going to vote against this; however, if more customers vote on it we can reconsider.
Here is what is going on :
Copy and paste does exactly that - it copies a file, exactly, then creates a duplicate of it somewhere else. If we add a refactor step to it - then it's no longer copy / paste. Everyone knows what copy / paste is and expects that. We would be changing what people expect.
I propose a different option, currently we have 'Move...' and move Refacotring - which are similar to what is described in this ticket. We can just add a key binding to similar to "Move ..." called 'Paste and Refactor'.
So you:
1: 'Copy; file
2: Instead of 'Paste' you use 'Paste and Refactor"
How's that?