LabView wants to OverWrite VI's not changed

[mbone206]

Thank You Greg & Joe

Greg: Is there an easy way to know if you accidently written over library vi

Mark

[Greg McKaskle]

At the time of the save, there is a link in the Save dialog for details. They are somewhat generic, but will tell you what the modification is. This is usually enough to make you comfortable clicking save or Don't Save.

After the file is saved, a diff with an official file is the only way I can say for sure. Unless you opened up vi.lib files and made your own edits, it is very unlikely that you caused an issues. I'll go with Joe's explanation.

I would encourage you to look at the Files tab and determine where your source is coming from though. The LV project has a way of trying to help you by adding links to files that are in locations you didn't realize. Then later, you'll clean up your hard drive and boom goes the dynamite -- your project is broken.

Greg McKaskle

[Joe Ross]

Originally Posted by Greg McKaskle

At the time of the save, there is a link in the Save dialog for details. They are somewhat generic, but will tell you what the modification is. This is usually enough to make you comfortable clicking save or Don't Save.

After the file is saved, a diff with an official file is the only way I can say for sure. Unless you opened up vi.lib files and made your own edits, it is very unlikely that you caused an issues. I'll go with Joe's explanation.

Here's an example of the changes list for a WPILib VI after an update.

[mbone206]

Thanx again Greg & Joe

Joe: That is a good example to look out for....