From 04:00 PM CDT – 08:00 PM CDT (09:00 PM UTC – 01:00 AM UTC) Tuesday, April 16, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Oops, said 'yes to all' ... does it matter?

Hi!

I just closed a VI and accidentally hit the 'yes to all'
button and labview saved a while bunch of other VIs ...
I didn't make any changes but do I now have to be concerned
that the utility VIs will not behave as expected?

Rudolf
0 Kudos
Message 1 of 2
(2,266 Views)
Rudolf,

Most likely you have nothing to worry about:
If you know that you didn't make any changes to the sub-vi's, then what
most likely got saved was the paths to the referenced vis. Whenever you
open a VI on a workstation and the VI references sub-VI's, labview looks for
those sub-VI's in several places. First is the saved location (where the
sub-VI was the last time labview opened this file) and if the sub-VI is not
found there (for example, I check a set of VI's out of source safe after
someone has modified them, but I check them out to a different directory)
labview then has several directories where it searches for the sub-VI's.
Then when you exit, the paths are saved and the sub-VI's updated, even
though you didn't make any code changes.
Ano
ther case where "changes" may be saved where none were made is if you
open a VI in a different version of labview. Example: I create a VI in LV
6.0 and you open it with 6.02. You may be prompted to save, even though no
changes were made.

~Petr~

"Rudolf Potucek" wrote in message
news:a3seqn$vo2$1@nserve1.acs.ucalgary.ca...
> Hi!
>
> I just closed a VI and accidentally hit the 'yes to all'
> button and labview saved a while bunch of other VIs ...
> I didn't make any changes but do I now have to be concerned
> that the utility VIs will not behave as expected?
>
> Rudolf
0 Kudos
Message 2 of 2
(2,266 Views)