Another thing not to do (Show Hierarchy view feature)

[JÞB]

I may make this my weekly boneheaded bug.  I inadvertantly dropped a sub-vi on a block diagram today that the calling vis call chain.  LabVIEW correctly broke my vi since the sub was not reentrant.  Bonehead me then figured it should be easy to find the reason by View>> Vi Heirarchy .   This was probable a mistake in judgment on my part.  The result "LabVIEW has encountered a problem and needs to close."  While this feature prevented the IDE from triing to do the impossible I feel it could have been handled a bit more delicatly.  Like, by disabling the Menu option while the error existed or just a pop-up saying "what were you thinking bonehead?"

[GregFreeman]

---

@Jeff Bohrer wrote:

I may make this my weekly boneheaded bug.  I inadvertantly dropped a sub-vi on a block diagram today that the calling vis call chain.  LabVIEW correctly broke my vi since the sub was not reentrant.  Bonehead me then figured it should be easy to find the reason by View>> Vi Heirarchy .   This was probable a mistake in judgment on my part.  The result "LabVIEW has encountered a problem and needs to close."  While this feature prevented the IDE from triing to do the impossible I feel it could have been handled a bit more delicatly.  Like, by disabling the Menu option while the error existed or just a pop-up saying "what were you thinking bonehead?"

---

Maybe that is NI's way of providing negative reinforcement 

[Nathan-P]

Which version of LabVIEW are you using?  I just did the same thing in LabVIEW 2012, and the VI Heirarchy shows the recursive loop.  (Vi1 -> Vi2 -> Vi3->Vi1...etc.)