>General question on VI modification

[Yixiao-uncle]

Hi.

I developped a very complex VI in order to acquire plant data from netDDE connection,  perform manipulations as averages, display data on front panel, and also display digital camera images on front panel. This VI seems to work properly and We use it from long time. Anyway everytime I stop my test session and close Vi, Labview asks me to save the Vi.

If I save or not, the following time Vi runs properly.

Now my more generic question is: how to  know the modification done on any Vi in order to decide if save modification or not?

Of course concerning my application it is not important at all if I save or not, but in order to have a "clean" software I would like to avoid that question Labview asks to me.

Thank you very much.

Antonio

[dan_u]

Hi Antonio,

you can list the unsaved changes when closing a VI. If the VI appears as modified just after opening it it's likely that one of its SubVIs is still saved in an old LabVIEW version. A mass compile might help in this case.

Anyway, check the unsaved changes and go through them to see where the problem lies.

Hope this helps,

Daniel

[smercurio_fc]

Well, you're not really building an application, as you're running the VI in the development environment, which is why you get that. You should consider creating an executable. Another reason why you may be getting that is if an interface that your code uses was updated. For example, I use MSXML for reading/writing XML files. That interface changes when MS updates MSXML for security fixes, and LabVIEW updates the code to reflect this, and tells me that the subVI needs to be resaved. In this case this is expected behavior.

[Yixiao-uncle]

Daniel, SMercurio: thank you for your answers.

I will try to make executable file.

Anyway just for a deeper understanding of Lv, please find attacched the changed list. AsYou can see only a cosmetic change has been done in front panel.

In my front panel there are two "image" objects: a jpg file representing plant sketch and image coming from digital camera. Even I accept to save changes, after opening the vi again and running it without changing anything, that "changed message" will appear when closing the Vi.

Any suggestion about what has happened?

Antonio

[smercurio_fc]

Hard to tell without actually having the VI. On rare occasions a slight corruption of the VI's front panel can cause this behavior. I don't think that's what's going on here. Is one of those controls/indicators and ActiveX control? Can you post your VI?

[matteobr]

Dear Antonio,

SMercurio get the reason telling you to create an executable file.

However, in the LV enviroment, also small cosmetic modification cause the VI to prompting you asking a save file.

This is how it works and how it is conceived.

Matteo

[smercurio_fc]

Yes, but the issue here is that the user saves the VI, and then when he goes to open it again it says the same exact thing: cosmetic changes have occurred and it needs to be saved. This behavior has been seen on other occasions. I don't think this is how it was conceived to work.

[Yixiao-uncle]

More details if the discussion is interesting.

In all  previous versions of my Vi, all is working properly and LV doesnt show me that message.

In the last version, that one we are discussing about, I added the image coming from a firewire camera. For some reasons  camera acquisition procedure is performed by another Vi.

Then I used global variable to send frames to my complex data acquisition Vi.

It is the only difference i can notice. May the use of global variable be the cause of that "changed Vi" message?

Thank You

[Ben]

---

antonio ferrante wrote:

... I added the image coming from a firewire camera. ...

---

I have seen issue with those imbeded object ofn FP causing this message. The CW 3d graph will do this asl well.

If you get rid of the image on the FP, does that illiminate the Q to save?

Ben

[Yixiao-uncle]

Yes, Ben.

Attached You can see a part of diagram I suppose to be responsible of change (it is marked by an arrow).

If i delete that while loop, Labview will not ask me to save  changed Vi.

Now I suppose there is no solution for this problem, anyway I learnd something more about Labview.

Antonio