LabVIEW Idea Exchange

About LabVIEW Idea Exchange

Have a LabVIEW Idea?

  1. Browse by label or search in the LabVIEW Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click Post New Idea to submit a product idea to the LabVIEW Idea Exchange. Be sure to submit a separate post for each idea.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see in a future version of LabVIEW!
Showing results for 
Search instead for 
Did you mean: 

Switch-A-Roo Two Wired Terminals

I love the built in switch-a-roo tool on block diagram objects.  Basically the rules is if you have an object on the block diagram with two inputs, and they are both wired, by holding CTRL and clicking on one of these terminals, the inputs will be switched.  This is great for things like subtraction, or division when you get the inputs backwards.  This feature also works on the select function swapping the T and F inputs.


But what this idea is about, is to swap two inputs in the same way it currently does, if you only have two inputs wired, but the function has more than two inputs.


There are times when I have two things wired to a subVI and that sub VI and I want to swap the wired inputs, but the function may have other optional inputs that are rarely used.  Because the function doesn't have exactly two inputs, the switch-a-roo tool won't work.  Or maybe it has other inputs that I just haven't wired yet (like error) but the two inputs that are wired need to be swapped.

Proven Zealot

Is this idea significantly different from this other idea submitted yesterday?

Proven Zealot

You know I did searching first but "Switch-a-roo" and "Switch a roo" and "Switcharoo" are all different to a search engine.  Maybe a mechanism of switching any two arbitrary wires or inputs is a better idea and would cover this use case.


I guess the closes existing idea is the linked one in the one you mentioned.


Still that one seems to have lots of discussion and while I like that, it makes it difficult to vote not really knowing what NI would choose to implement if they choose to work on that idea.

Proven Zealot

> not really knowing what NI would choose to implement if they choose to work on that idea.


That's easy: None of the above.


For any of these, the Idea Exchange serves more to tell us "this is an area that needs addressing." We start with an idea proposed by the community, but after testing it on a prototype, it may change significantly. There may be use cases that aren't even addressed in the community forum. When you're adding kudos, it is both "do something like this" and "do exactly this", and you can clarify in the comments if that's important.

Proven Zealot