Reentrant VIs - disappear?!!

[Miguelón]

Debugging with Labview 8.6.1, sometimes, when you think you have closed completely a VI, it keeps running but

it doesn´t appear in Labview so it is impossible to "re-close" it . The bad thing is that you have to quit LabView because the linked SubVIs are

unable to enter in edit mode.

When you close Labview, it recognizes that the VI is running somewhere.

In very large programs, this fact is very upsetting

Does anyone knows any solution?

Thank you

[PJS]

When I do operations that are opening reentrant VIs that do not have a remote stop, I track the refnums that I open.  Sometimes even storing them in a global array of vi refnums... Then when I need to insure everything closes, I use those references to an abort method and close reference without the error clusters being wired, since I ONLY want them to stop and don't care if they already have stopped (which would generate an error).

Hope that helps some.

[Been bitten by LabVIEW · Accepted solution]

If  you want to know what VIs are running in development only, you can either use the Show VI Hiearchy which will show all of the VIs, including the top level (at the top of the diagram).

Alternativly, I use find. Because the VI has an open refnum, find can search through the VI.  I use this to access the Block Diagram when I don't have access to the menu command on it's FP.  Since most of my block diagrams have the word poll, I search for that, and change the search scope (that should show all VIs with an open reference) to the VI I want to search.

Tracking all opening of VIs like mentioned above is also a good way of ensureing you don't forget to close them.

Hope this helps.

A

[Miguelón]

Thank you very much !!!!

smileyvery-happy: