LabVIEW 2020 Not Saving Overrides Correctly

[McQuillan]

Hey Team,

I've already submitted this to NI as a CAR/SR but to speed up the process I want to see if others have experienced the issue of having Override VIs saving incorrectly? Or if anyone had ideas as to why it could be happening.

When creating a VI for override, the actual VI saves on disk but only the first 'save' seems to work. As far as I can tell, this behavior is sporadic, but it happened often enough for me to realize it wasn't just a case of me not saving. (I was 'lucky' enough to have it happen on the first time recording the video).

• LabVIEW Professional 20.0, the video was recorded with 32-bit, but I first noticed the issue with my  64-bit version.
• I have witnessed this behavior on two laptops (one LV20 32-bit and the other 64-bit), however, they both have similar LabVIEW plugins installed. However, none of those were issues in previous versions of LabVIEW

The following video shows:

1. Creating three VIs for override
2. Saving Method 3.vi after altering it
3. Altering Method 2.vi and doing a Ctrl+Shift+S to save all (saving Method 2 and Method 1)
4. Altering Method 1.vi and clicking the save all button on the project
5. After restarting LabVIEW, Methods 2 and 3 are as expected, Method 1 appears to be the standard Override template.

[McQuillan]

I've just tried this with a version of LabVIEW I haven't messed around with* on my laptop (LabVIEW 20.0 32-bit), and I'm getting the same results

*I have a couple of toolkits installed, but I haven't added any project providers, RCMs, or altered the DD Template.

[McQuillan]

I installed a fresh copy of LabVIEW 2020 on to a fresh W10 VM and the same thing happened! What the heck?!

As a sanity check, I did the same thing in LabVIEW 2019 and everything worked as expected - So I'm ruling out the newest windows update. The big main difference is how the child class is created with the new dialog box.

[crossrulz]

I am not seeing this with my LabVIEW 2020 Community Edition.  I don't have nearly as many VI packages installed as you, so maybe there is a conflict in there.

But something I noticed in your video.  Did you save Method 1 before closing it?  Your list of actions says no, but I didn't see a dialog to save Method 1 when you closed it before hitting the Save All.

[crossrulz]

---

@crossrulz wrote:

But something I noticed in your video.  Did you save Method 1 before closing it?  Your list of actions says no, but I didn't see a dialog to save Method 1 when you closed it before hitting the Save All.

---

Yep, that is the cause.  I just manged to get it to reproduce.  Something is keeping Method 1 from realizing it changed.  I'll try a few more things to see if I can narrow it down some more.  My current theory has to do with the Save All after altering Method 2.

[billko]

---

@crossrulz wrote:

---

@crossrulz wrote:

But something I noticed in your video.  Did you save Method 1 before closing it?  Your list of actions says no, but I didn't see a dialog to save Method 1 when you closed it before hitting the Save All.

---

Yep, that is the cause.  I just manged to get it to reproduce.  Something is keeping Method 1 from realizing it changed.  I'll try a few more things to see if I can narrow it down some more.  My current theory has to do with the Save All after altering Method 2.

---

I'm no expert in overrides, but I feel like an expert with "Save All".  It just doesn't.  "Save all", that is.

[crossrulz]

I actually managed to get this reproduced with 1 method.

1. On the child class, right-click and choose New->VI For Override.  Choose a method (only need one) and create it.

2. Save the VI.

3. Change the VI in some way (remove the Call Parent Class Method, add functions, etc.).  You will notice that the "dirty dot" doesn't come up in the VI's window title bar.

I'm now trying to figure out how to get the "correct" behavior where it saves the VI regardless.  But that will need to wait.  I actually have to get some work done now.

[McQuillan]

Thank you for your comments!

For clarification and simplicity, I have re-recorded the video with key-strokes so you can see exactly what I'm doing.

You are right! The VI doesn't show the * to say it's been modified! Also, the Run Arrow is broken until I "Save" it

[AristosQueue (NI)]

Finally replicated. Not sure what's wrong yet, but at least I have it trapped under a debugger.

[McQuillan]

That's great, thanks for keeping us updated 🙂