Prevent overlapping objects

[Yamaeda]

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.

<story>

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!

</story>

/Y

[AristosQueue (NI)]

Duplicate:

http://forums.ni.com/t5/LabVIEW-Idea-Exchange/LabVIEW-should-break-VIs-which-have-hidden-code/idi-p/...

Related:

http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Don-t-Allow-Hidden-Wires/idi-p/1687770

[Darren]

Duplicate of http://forums.ni.com/t5/LabVIEW-Idea-Exchange/LabVIEW-should-break-VIs-which-have-hidden-code/idi-p/...

[X.]

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