LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Why is my project permanently "dirty"?

Hmmm.  The project includes a folder called "Libraries" which mirrors a real folder called "Libraries".

 

If I delete that folder from the project, then save the project, close it and re-open it, it's not dirty,

 

If I drag the folder back into the project, save the project, then close it and re-open it, it's dirty.

 

Since <a href="http://forums.ni.com/ni/board/message?board.id=170&thread.id=234001&view=by_date_ascending&page=1">this post</a> basically gave me no reason to keep things in the project, I'll just dump it and move on. 

 

 

[ yes, I see that the link doesn't work.  This forum rejects legitimate HTML and offers me a link edit thingy, which turns into a blank window.  Really helpful. ]

Message Edited by CoastalMaineBird on 09-30-2008 03:57 PM
Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com


LinkedIn

Blog for (mostly LabVIEW) programmers: Tips And Tricks

0 Kudos
Message 11 of 14
(886 Views)

[ yes, I see that the link doesn't work.  This forum rejects legitimate HTML and offers me a link edit thingy, which turns into a blank window.  Really helpful. ]


This link?

 

🙂

Chris Bolin
LabVIEW Partner Program, CLA
Message 12 of 14
(878 Views)

I am using Labview 2010 using classes and had the same problem. I tried running the dirty-dot utility found here: http://digital.ni.com/public.nsf/allkb/D4032A485C9F18C1862576D6007681F4 but the utility found nothing. I noticed in my project there was a file called visarc listed under the dependencies. I right clicked the vi and selected "why is this item in dependencies" which higlighted a vi in one of my classes. I then opened the vi and clicked save. When I saved the vi I noticed for a split second the vsarc file disappered from my project then reappered. After doing a save all on my project, I no longer have the constant unsaved changes warning. Hope this helps anyone else experienceing this problem

0 Kudos
Message 13 of 14
(669 Views)

Hi, 

 

I'm not sure if my comment will help, but I was having the same problems this week, and it was the same visarc file which showed up only when some vis were open.  Your solution didn't sort the problem out, but I added the visarc to the project and the dirty project became clean straight away.

 

Best regards,

danidpr

 


 

 

Certified-LabVIEW-Associate-Dev_rgb.jpg

0 Kudos
Message 14 of 14
(638 Views)