VIs immediately tagged dirty on open

[wildcatherder]

If all I do is open a VI- I don't even click the mouse, change views or ANYTHING, it gets the asterisk in the title showing it has been changed.  But nothing has changed. 

How do I stop this behavior which includes asking me if I want to save on close?

[crossrulz]

Do you have the "Seperate From Compiled" turned on for the VI?

[wildcatherder]

I've never set that property, so it is set to whatever is the default value.

[crossrulz]

Then that is likely your problem.  If something in a subVI changed, that would cause this VI to have to recompile, therefore causing a change in the file.  If you have the seperate from compiled turned on, then the compiled code is not saved with the source code and you will not need to resave just due to a subVI changing.

There is an option to have it on be default.  I highly recommend using that.

[wildcatherder]

I haven't changed anything in a sub-vi.  I start LabVIEW open a sub-vi and it is tagged dirty.

[RavensFan]

What does "List Unsaved Changes" say?

[P@Anand]

How to Check "List Unsaved changes"?

[GerdW]

Hi PAnand,

close the subVI without saving it before. Then LabVIEW will ask you for saving with presenting a dialog where you can "check for unsaved changes"…

[P@Anand]

---

@GerdW wrote:

Hi PAnand,

close the subVI without saving it before. Then LabVIEW will ask you for saving with presenting a dialog where you can "check for unsaved changes"…

---

Thanks Gerd I never noticed before.

[crossrulz]

---

P@Anand wrote:
How to Check "List Unsaved changes"?

---

Also in the VI Properties window is a "View Unsaved Changes" button.