save changes when there are no changes

[wb2nvy]

Why is it that when I open a subvi and close it making absolutely no changes, I'm prompted to 'save changes'?

[GerdW]

Hi wb2nvy,

who knows?

Maybe due to

- changes in referenced files

- loading a VI from an older LV version, so recompilation occurs

Have you check why LV wants to save? You always have to option to do so...

Message Edited by GerdW on 06-02-2010 02:47 PM

[H_SH]

usually this happens due to VI recompile on open and close... but yeah you can check the reasons by click on list unsaved changes on dialog box..

hope it helps

HS

[wb2nvy]

In this new main vi, I'm building it in LV2009, but using all subvi's that were made with LV8.5. I've saved and run the main vi several times in development mode. Doesn't that automatically update all subvi's to LV2009?  I don't understand why 8.5 subvis aren't automatically recompiled to the same LV rev as the main vi, or at least generate an error message.

[GerdW]

Hi wb2nvy,

why should LV save those subVIs on it's own? You may have to check the old subVIs for changed functionality before saving... (Compare this to a C development environment: when you change one main.c-file do all other sub.c-files get saved?)

Why should LV generated an error message, when the old subVI is executable? You already get a warning to save the recompiled VI...

Edited:

When upgrading to a new LV version I usually make a complete backup, then copy all VIs to a new folder, then do a MassCompile for this folder. Now you have all VIs in the new version and get all possible warnings for changed behaviour...

Message Edited by GerdW on 06-02-2010 03:24 PM

[H_SH]

Hey wb2nvy,

There is one document explaining to mass compile VIs... or forced recompile ... May be something you like to read ..

Regards

HS

[wb2nvy]

Thank you H Sh. I checked the first link you attached and found this:

"When you open a VI last saved in a previous version of LabVIEW, LabVIEW automatically converts and compiles the VI. You must save the VI in the current version of LabVIEW "

So when I save this main vi (after it is automatically converted and compiled), it apparently only saves the recompiled MAIN vi and not the subvis that comprise it, correct? All the previous version subvis remain previous version unless I specifically recompile them separately, or do a mass recompile? Why would anyone NOT want to include the subvis when the main vi is recompiled to a newer version?

[H_SH]

Ans to your first two question is YES and then ans of third one is, it is same like most of coding language i know..  you have the option in LabVIEW to mass compile ..

[GerdW]

Hi wb2nvy,

"Why would anyone NOT want to include the subvis when the main vi is recompiled to a newer version?"

Maybe you have linked to subVIs also used with the older LV version and so don't want to save subVIs automatically?

As said before: no other IDE I know of automatically saves referenced files to a newer version...

And:

You should get asked to save subVIs before closing the mainVI. You always have the option to save them. You always are presented with reason why LV wants to save. You always have to decide between saving or not saving... You always have the mass compile option.

It's your duty to decide when to upgrade VIs - LV will and cannot take that decision!

Message Edited by GerdW on 06-02-2010 04:37 PM

[MF]

I have a large program and lately, everytime I open the main file it recompiles it and when I exit without making any changes, it wants me to Save the file. I have not upgraded or changed the LabVIEW application. If I Mass Compile or do a "Save All", I still am prompted to Save the VI before exiting.

I checked the "List Unsaved Changes" and the "VI Recompiled" and "sub vi call(s)" are shown as being the changes right after I do a "Save All".

I am using LV 8.5 on an WinXP PC. Any help with this annoying problem would be appreciated.

Michael