Why is my project permanently "dirty"?

[CoastalMaineBird]

My project has recently become permanently "dirty".

By "dirty", i mean:

-- There is an asterisk next to the file name in the title bar.

-- If I close it, it warns me about unsaved changes.

If I ask it to LIST UNSAVED CHANGES, it tells me:

 "An attribute of the project was changed."

The details for that change say:

 "An attribute of the project was changed."

Gee, thanks.

If I SAVE it, the asterisk goes away, but when I open it again, it's back. 

It's a dual target project with PXI as one target.

FWIW, There are a few VIs which run on both sides, with conditional compilation symbols to modify the behavior slightly.

Any ideas? 

[Eugen_Graf]

It happens me too, I am very interested in answers.

I don't use PXI or other NI hardware. Thank you for this topic, Eugen 

[CoastalMaineBird]

I'm on LV 8.2.1 BTW.

[Neil.Pate]

Do you have any autopopulating folders in your project?

This seems to cause the dirty asterix indicator to be perpetually set!

[CoastalMaineBird]

I never heard of "autopopulating folders" .

Must be what Mac calls "smart folders".

According to Google, they were introduced in LV 8.5

I'm on LV 8.2.1 

[Neil.Pate]

As it (autopoulating folder) is part of the LV project I am surprised NI give them a different name between different operating systems.

But, sorry, I can't be of further help then. 

[CoastalMaineBird]

You misunderstand me.

"Smart folders" are a system-level construct in Mac OS X - they have nothing to do with LabVIEW.

It's just that the idea is the same.

In any case the autopopulating folders don't exist in LV 8.2.1, so that's not it. 

Thanks for your thoughts. 

[Ben]

---

CoastalMaineBird wrote:

My project has recently become permanently "dirty".

By "dirty", i mean:

-- There is an asterisk next to the file name in the title bar.

-- If I close it, it warns me about unsaved changes.

If I ask it to LIST UNSAVED CHANGES, it tells me:

 "An attribute of the project was changed."

The details for that change say:

 "An attribute of the project was changed."

Gee, thanks.

If I SAVE it, the asterisk goes away, but when I open it again, it's back. 

It's a dual target project with PXI as one target.

FWIW, There are a few VIs which run on both sides, with conditional compilation symbols to modify the behavior slightly.

Any ideas? 

---

AS usual your "gut" has served you well. The acual culprit(s) could be hard to say but the most common reason is the error handling VI's. Error codes can be defined from a bunch of places but a different set of drivers OR hardware targets will result in the General Error Handler getting updated so it reports properly on the target is runs on.

Just trying to help out,

Ben

BTW: This behaviour irritates me since I count on the asterisk telling me if I changed something.

Message Edited by Ben on 09-30-2008 07:45 AM

[CoastalMaineBird]

I'm not sure I understand you.

Since this project began, I've used the GENERAL ERROR HANDLER in both targets.

On PXI, I use it just to translate error codes into strings, which I ship back to the host via TCP.

It has always asked me to SAVE this VI, along with my own conditionally-modified ones, depending on which target got saved last.

That's because it saves the compiled code with the VI, and the code is different depending on the target.

I see warning messages about things in the ERROR HANDLER which are "not available on the current target". 

I understand that.

But that has never caused the PROJECT ITSELF to be dirty.

That has only come about in the last couple of days.  And I've made too much progress to backtrack. 

[CoastalMaineBird]

I'm not sure if it's relevant, but here's another detail.

I added a VI recently (about the time this started happening, come to think of it).

I accidentally created it for the HOST target, but I switched it to the PXI target for use.

Now when I deploy, I sometimes (not every time) get a message that this VI has unsaved changes.

When I LIST UNSAVED CHANGES, the CHANGES box is empty.

IOW, it thinks the VI has changed, but is unable to tell me where/what.

Weird.