cut (ctrl+x) then paste (ctrl+v) does not move like in may other software packages

[tshurtz]

In many software packages, if you do a cut (ctrl+x) then paste (ctrl+v) it will move the item and then sometimes subsequent paste operations will make copies (sometimes they act like the clipboard is empty after a single paste)

In labview it is more like it makes a copy and deletes the original. This is somewhat unexpected behavior for me (maybe others find it normal). I would like to use it to move items around without having to drag somewhere in between (say if I want to move a terminal or local variable from one case to another I have to drag out while braking wire connection change cases and drag back in)  

For a control, if it had property nodes, connections in connection pane, events, or local variables all these connections brake or are deleted, and the new item is no longer connected to anything. If you do it on a property node, the new node is un-linked to anything. A local variable is the worst of all in my opinion. It deletes the original local variable but makes a new control that the new local variable is linked to. this seems like it would rarely if ever be desired behavior (you get the same problem just copy/paste on local variable as well). On the other hand just making a new local variable linked to the same control would be great for both cut/paste or copy/paste. 

[AristosQueue (NI)]

Paste-replace is a rather critical operation for LabVIEW, one we are unlikely to want to mess with. Copy (or cut) a control, select a second control, then paste -- it replaces the selected control. That keeps all the connections (wiring, conpane) of the original intact.

Paste-at-last-click-location is also rather critical. Paste, when there is no selection, pastes where you made your last click. This allows you to position inside of objects without affecting any autosizing bounds and without the code showing up in places that stack on top of other things that you are trying to wire to. Also on paste, we always select the newly pasted item(s).

In the case of ctrl+x followed by ctrl+v, both of these features become counterintuitive. So what you're asking for is special behavior that applies only when we are doing a ctrl+v directly after a previous ctrl+x or a previous ctrl+v. That seems doable... do you think it would be more confusing to have different behaviors for the first ctrl+v than for the second?

The most nuanced behavior would be this case: Suppose you select a string control and hit ctrl+x. Then you select a numeric and do ctrl+v... numeric gets replaced by string. You do ctrl+v again, and you get a new string. Confusing or expected?

[tshurtz]

I was completely un-aware of pasting into another control. That is really cool and understandably complicates things. My desire was only for cases where you paste with noting selected. I don't know how to deal with the other cases but i would be fine with if you do a ctrl+x then you get one paste either into something or as a new entity. Then it is off your clipboard if you want another do a ctrl+c at first or after not ctrl+x. I think that if you want to get something on your clipboard for multiple pastes and get rid of the original (less likely that a desire to move in my case) you can always ctrl+c then delete