Dynamic Dispatched VIs staying in run mode

[Nitin_T]

This thread is to discuss the question/problem mentioned in the following post. More information to be available soon.

[Burt_S · Accepted solution]

This was reported to R&D (# 157033) for further investigation. I noticed in your original post that you mentioned that the project will not prompt you to save any edited VIs when closed.  I however have not been able to reproduce this behavior.  The project will always prompt me to save any of the dirty VIs.  Even the VIs still in run mode.  Is there perhaps a corner case that I am missing that is preventing me from reproducing this?  Also, thanks for the feedback!

[Chris_VH]

---

Burt S wrote:
This was reported to R&D (# 157033) for further investigation.

---

Since it was R&D that posted this, I bet he knows already

[kegghead]

I created the project in 8.6, could a version change to the more recent 8.6.1 force a recompilation and trigger a save? I'm planning on installing the Q1 software soon, so I will be able to confirm this I suppose. Also, to ensure we're working with the same code base,  the example can be found in Post #8 on this lava thread.

[Ben]

---

Burt S wrote:
This was reported to R&D (# 157033) for further investigation. I noticed in your original post that you mentioned that the project will not prompt you to save any edited VIs when closed.  I however have not been able to reproduce this behavior.  The project will always prompt me to save any of the dirty VIs.  Even the VIs still in run mode.  Is there perhaps a corner case that I am missing that is preventing me from reproducing this?  Also, thanks for the feedback!

---

Options >>> Environment >>> Do not save automatic changes

Is often checked when using source control.

That setting affects if you are prompted to save changes.

Don't know if it is realted but I'm just trying to help,

Ben

[Burt_S]

I originally opened the code in 8.6 and got it from your original post.  Perhaps that preference is checked as Ben mentioned?  Will any other project you open prompt you to save automatically when closed?  Also, can you properly save the project before closing it?

[kegghead]

Well, my SCC isn't integrated into the LabVIEW IDE, I use Tortoise SVN. I doubt those settings would affect me since my SCC doesn't actually use file locking. Regardless, I've ensured the "Treat read-only VIs as locked" box is checked, however the  "Do not save automatic changes" box is not. I checked out the current revision and copied a dependency (An Open Error VI) in case there was a version difference between our systems. The resulting version is attached. As far as I can tell, nothing is being modified when opening the project in 8.6 and the behavior described in the original lava post persists.

[Burt_S]

I am still unable to reproduce the save problem that you are having.  Do any of your other projects give you a save problem?  Can you manually save the project successfully before closing it?  I would like to figure out if this is a seperate problem entirely or just a difference in our configurations.

[kegghead]

---

Do any of your other projects give you a save problem?

---

I can't really answer that since I'm not really sure what the problem is. Usually I can save dirty VIs, even if they're running when I try quitting. I will always be prompted if I try to quit with unsaved changes. In this situation, it does not appear there are any dirty VIs...

---

Can you manually save the project successfully before closing it?

---

It does not appear so. Manually doing a Save All or a Save All (this Project) operation at the project level appears to do nothing, as the timestamps on the files at the OS level do not change. I'm assuming that these operations are not intended to overwrite files that have not changed? I've tried to duplicate the project heirarchy through a Save As operation, but that fails miserably as the operation attempts to save the same classes multiple times.

Which files are being modified when you open the project?

[Burt_S]

Interesting, so this is what I am doing.  I open up your project.  Then I make changes to the Basic Message Pump.VI (the one that won't go into edit mode) by simply moving a wire on its block diagram.  Then I run and stop the Example 1.VI.  After it stops running, I close the project and LabVIEW opens the 'Save Changes?' dialogue with the Basic Message Pump.VI (or any other VIs I change) in the list of VIs to save.  I am doing all of this in 8.6.  Does your project give you different behavior than this?