LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Every time I open my project file (LabView 8.5) it needs to be re-saved

I expect that when LabVIEW opens the project file, it searches those autopopulating folders to add or remove any new or removed files in the folders.

It appears that LabVIEW doesn't confirm that it made any changes in those folders and automatically sets the change bit for the project.
Message 21 of 28
(1,572 Views)

I vote that Matthew has won this round. (Nice play with the Auto-populate move. It caught me off guard)

What do you think Ed?

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
Message 22 of 28
(1,566 Views)
Thank you for the kind words Ben.
0 Kudos
Message 23 of 28
(1,561 Views)

Matt & Ben (a new ice cream?), you've both been great. Thanks. I'd just be guessing, but what you say sounds reasonable. I think it's obvious that I don't change the contents of those folders very often, nor would any developer, for the most part.

If LabView doesn't realize that there are no changes, but it flags it as if there are, then, to me, that's an undesired operation (or in the vernacular, a "bug"). NI moderator, any comments? Maybe we should submit this as a possible bug. What do you guys think?

0 Kudos
Message 24 of 28
(1,551 Views)

NI AE,

Please verify that the behaviour reported above re: Auto-populate option requiring saves is correct. if not please post a CAR for this issue.

I believe I have noticed this same behaviour on my machine running under LV 8.5

Thank you,

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 25 of 28
(1,539 Views)

I created an SR number and called NI to "submit" this possible bug. The apps engineer is going to research it and get back to me. I'll post what he replies.

BTW, the fact that some of my vi's were originally from the 8.2 branch was of no consequence, I was told. When I saved my application as an 8.5 version, all vi used are "converted" or updated to the current version (within my vi). (By that I mean that the vi's in the 8.2 branch are not touched, of course, otherwise they wouldn't work in the 8.2 development environment.)

I'll keep you posted...Smiley Happy

0 Kudos
Message 26 of 28
(1,520 Views)

Hi everyone.  I am the AE who is working on this issue.  I have been able to reproduce the problem rather easily.  This has been reported to R&D (109768) for further investigation.  Thanks for all of the help.

Adam H.



Message Edited by Adam_H on 05-15-2008 11:54 AM
Adam H
National Instruments
Applications Engineer
Message 27 of 28
(1,486 Views)

Thank you Adam!

CAR's (without having to fight) are always worth 5-star ratings in my book.

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 28 of 28
(1,463 Views)