From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
YES, I want better information when there is hidden code on my diagram, but...
NO, I don't want my code to break!
The Idea:
If a structure hides code beyound it's boundary, then provide a visual indication. For example, the edge of the structure could be coloured red to alert the user that something unexpected is going on.
I should also point out the main objections I had to this idea:
Code can be hidden in other ways as well (behind structures, under other nodes or VIs) and this won't cover those.
The hidden code might be in an unopened subVI or another part of the diagram and you won't know it's there unless you actually have the structure in front of you. This isn't a big deal if the hidden code doesn't do anything, but if it creates a bug (especially one which is not obvious), you would want to know it's there even if you're not actually looking at it.
> This idea makes no mention of "other" hidden code
No, but that doesn't mean the issue can be ignored. If the idea only solves part of a problem, than it's possible that it should not be implemented and that something else which does solve the rest of the problem should be implemented instead.
I'd prefer it'd be impossible to hide code that way. No structure should be able to minimized so it happens and blocks should be pushed away from each other if dropped over each other.
A indication would be an acceptable 2nd option. :)
/Y
G# - Award winning reference based OOP for LV, for free! - QestitVIPMGitHub
Any hidden code should be avoided. The new "minimal energy BD auto arrangement method" idea, presented by Jeff Kodosky at NIWeek 2012, would make visible everything automatically.