LabVIEW Idea Exchange
The crux of this idea is a very simple premise: Structures should not be allowed to hide code inside their diagrams. Ever. Period. There is no legitimate reason.
The rest is implementation details which are negotiable, unlike the basic premise.
With Autogrow enabled this is not an issue. So it could be as simple as removing the option to turn it off. I would prefer a slight alternative, allow autogrow to determine two different behaviors when an object pushes against a structure boundary: Autogrow = object wins and structure grows. No Autogrow = structure wins and object no longer moves. All structure growth is done by hand in that case.
When upgrading VIs which have hidden code, I suggest a one-time autogrow. Breaking code could be an option ( 
), but that would simply force the user to autogrow or cleanup the BD anyway. If there are other errors, a broken run arrow is not a clear, direct indication anyway.
There could be a corollary preventing hidden code in general. I may not agree with them, but I do see that there could be an argument there to allow hidden code in some cases. That battle is being waged elsewhere:
I see no reason, however, to allow the bounds of a structure diagram to shrink beyond the bounds of its content. Nefarious reasons? yes Legitimate ones? not that I can think of.
I empathize and support this idea as a start:
But I do not want a visual indication, I want to know by construction that nothing lies beneath.
