Losing changes in LabVIEW 8--bug report

Question

Don't know if this has been reported yet or not but it was driving me crazy making my coding changes evaporate until I started realizing it wasn't me.
To reproduce:
Create a blank project and a new VI
Add FP.Open VI Property node with a False Constant
Run the VI
All changes will be LOST
After nearly going mad and tracking down the root cause, I find the newly added note:  "National Instruments recommends using the Front Panelpen [or Close] method instead of this property."
So you can try that too if you want, which has the same results:
Create a blank project and a new VI
Add FP.Close Method
Run the VI
All changes will be LOST
*POOF*  If the VI was an Untitled new VI that hadn't been saved, it will just vanish from the project list.

Answer 1

You're correct. I forgot one step to make the, "This
is
how we close instances of VI templates opened to avoid the Save
dialog." statement true. The VI must open a reference to itself and
pass that to the Node to avoid the Save dialog. 7.1 does indeed pop up
the Save dialog if you just have the Node set to close.
So now the question is, did NI intentionally change this or not. I've
found other changes that I thought were bugs that they intentionally
changed. See this thread for one of them.
I'll see if I can get the attention of an AE to look into this.
BTW, I do hit (Ctrl+S) before I run anything because I've had LabVIEW dissapear when I hit Run.
Ed
Message Edited by Ed Dickens on 05-03-2006 03:56 PM
Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.