LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
Zafer.Depe

CTRL+drag terminals

Status: Declined

Any idea that has received less than 6 kudos within 6 years after posting will be automatically declined.

 I have searched but couldn't find any idea about that. At block diagram, if we ctrl+drag any variable Labview creates a new copy of the same object but when we ctrl+drag any terminal it creates a new object (terminal). I rarely create a copy of the terminal from block diagram. Sometimes if the code is really huge and you put a terminal inside the code without being noticed when you drag that code it becomes hard to clear new terminals. I think it would be better if Labview creates the local variables of the dragged terminals. Front panel action and ctrl+C - ctrl+V should stay same.

 

NOW

ctrl_drag_before.jpg

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

AFTER

ctrl_drag_before.jpg

 

 

 

11 Comments
RavensFan
Knight of NI
elset191
Active Participant

I don't think so Ravens.  It appears to me that this idea wants to make ctrl+drag the same as copy and paste, where as the other one wants to make copy and past the same as ctrl+drag.

 

edit:

Actually, upon further review, this idea doesn't include copy and pasting locals at all.  He wants locals created when copying a terminal.  At any rate, I don't think it's a dupe.

--
Tim Elsey
Certified LabVIEW Architect
Zafer.Depe
Active Participant

"Actually, upon further review, this idea doesn't include copy and pasting locals at all. He wants locals created when copying a terminal. At any rate, I don't think it's a dupe."

 

Totally true. Actually ctrl+drag works fine for all variables, property nodes, structures,.. but not for terminals. I want them to change it for terminals. If you ctrl+drag terminal Labview should create a local variable of it. The other idea says ctrl+C - ctrl+V should do that. This is a choice but I frequently use ctrl+drag so i prefer if they change it for ctrl+drag.

RavensFan
Knight of NI

Okay.  Maybe it's not a duplicate.  But it is certainly looking at the same problem from the other direction.

Zafer.Depe
Active Participant

"Okay. Maybe it's not a duplicate. But it is certainly looking at the same problem from the other direction."

 

It seems the problem is almost same but copy + paste never worked as to create an exact copy of an object. Its main job is to create a new object with same characteristics. In some cases it creates a copy of the same object. So it should be better to change it for ctrl+drag. Because its main job is to create an exact copy except terminals. If they change it for terminals I think ctrl+drag wil work perfectly.

 

Anyways the idea should be combined with the other one but I insist on ctrl+drag.

Ray.R
Knight of NI

NO WAY!! 

 

I disagree.  I happen to often use Ctrl+drag to duplicate controls.   I would NEVER want LabVIEW to create a Local instead. 

 

Sorry to say so, but I disagree with your suggestion. This would only contribute to more Local abuse.

 

NO WAY!!

Zafer.Depe
Active Participant

"NO WAY!!"

 

CALM DOWN!

 

Nothing changed yet. This is just an idea, it doesn't have to be implemented. The core idea was to create local variables quicker instead "right click + menu  create + menu local variable". ctrl+drag is one of the most used action in labview and it creates exact copies execpt terminals. I thought if they change the action to create local variables, ctrl+drag will create exact copy of all objects inside the code. Front panel diagram actions and copy + paste should stay same so you can duplicate terminal by copy + paste as you can do now. The idea should be changed ctrl + shift + drag creates local variables of terminals but if they change it for ctrl + drag, the main job of the ctrl + drag will work perfect.

Ray.R
Knight of NI

"right click + menu  create + menu local variable" is quick enough.  You can always duplicate a Local by Ctrl+drag once a local is created.

 

However, there should NOT be a need for duplicating Locals.  Why would you want an easier method to cause potential race conditons and headaches?  

 

Let me ask you something.  How many locals do you have in each of your VIs?  What is the average count?

 

Your suggestion does not promote good programming practices.

Zafer.Depe
Active Participant

"Let me ask you something. How many locals do you have in each of your VIs? What is the average count?"

 

>> 1.000.000... 

 

I almost never use global, local, shared,.. variables. I just use them to give initial values to controls & indicators and show new values on the user interface. Sometimes to read a value from the screen or save the values from user interface, etc...

 

Anyways, you don't have to agree this idea. It is enough to explain why it is not necessary for you. This is my opininon, "ctrl+drag" is perfect to copy any part of the code and it should be better if it creates locals for terminals. It would be also a quicker way to create locals of it.

 

Never judge programming capabilities of someone. Noone has to be a perfect programmer as you o_O

Ray.R
Knight of NI

I was just pointing out my opinion that they should not change a good thing to make it bad 😄