[Bug report] - Closing the top level VI in a project silently discards the changes

[tst]

When you close a VI you edited in a project, you get the save dialog. I often choose the "Defer Decision" option, because I don't want to immediately save the VI.

The problem is that when the top level VI is closed, the VIs are silently unloaded from memory. If you have VIs where you didn't save your changes, you will lose these changes.

I attached a simple example (2009) which demonstrates the problem with a single VI. The problem becomes worse if you have subVIs.

[Smootastic]

Hi tst,

Did you install the 2009f2 patch? 

When I was testing, I created a new VI and then added your Demo as a SubVI.  When I edited it, I opted to defer.  Upon reopening the SubVI, my changes were still there.  When I did close the top level VI, I lost my changes if I opted to not save.  Does this sound right to your instructions?

[tst]

I thought I installed the patch, but then I realized I didn't, although it turns out that wasn't the issue.

The issue actually seems to come from the JKI right-click framework. It seems that for some reason it holds a reference to the VI, so that when you close a VI, LabVIEW thinks it's not going to unload it. I can toggle this behavior by starting and starting the RCF. I'll point this out to JKI, so they can investigate it directly.

[tst]

Turns out this was already reported here.