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: 

Prevent overlapping objects

Is there any instance where it's good/ok to overlap objects? It should be prevented by LV. If you drop an object on top of another object it should move it as needed to prevent overlapping.


It'd be similar to the Auto grow, but would apply to all moved/placed objects.



More by chance than anything i noticed a strange look on one VI in an old project and after a short investigation it turned out there were 2 VI's on top of each other! One had no inputs connected and this could explain some behaviours we've seen before, as this results in a race condition where one uses the default values.


At some time this VI was probably moved with Ctrl pressed as part of cleaning up the diagram ... had this suggestion been in place it'd have placed itself to the side clearly showing there were two!




G# - Award winning reference based OOP for LV, for free! ADDQ VIPM Now on GitHub
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
Proven Zealot
Trusted Enthusiast
Trusted Enthusiast

The "story" is not particularly illustrative, as you would have easily caught the problem if the VI's inputs had been set to "required".