VIs seem disconnected from project

[srb_Kinze]

Some of my VIs seem disconnected from the project.  I am using LabVIEW 2018 and in most projects if I have VIs open and close the project, the VIs close also.  I am also asked to save some VIs only after I close the LabVIEW getting started window, not the project.

[billko]

I admit I haven't seen this before, so I can only guess.  I think that if you open a VI in a dependency from Windows Explorer, it won't close when you close the project that depends on it.  If it was recompiled, it will ask you to save the VI when exiting LV.

[Bob_Schor]

I've not seen this, neither has Billko.  Why don't you find a Project that shows this (strange) behavior, compress its folder into a Zip file, and attach that file.  We'll take a look.  You might also mention the Version of LabVIEW (and whether you are using 32-bit or 64-bit LabVIEW).  Something sounds "wrong" (it may be something you are doing ...).

Bob Schor

[Yamaeda]

If you open some VIs Before opening a Project file, they'll be handled outside of the Project. Then you'll see this behaviour.

[paul_cardinale]

I've had this happen many times.  Never really dug into it.  What's happening is that after you close the project something is still in memory that depends on some VIs in the project and thus holds them in memory.

This tends to happen more often when VIs in the project use XControls.

Also, if you've copied any LabVIEW code to the clipboard, all the dependencies of whatever is in the clipboard are held in memory (you can clear that by just copying some non-LabVIEW item to the clipboard).