"New VI for OverRide" creates broken VI

[CoastalMaineBird]

LV2013 SP1

I have a parent class, in one PPL (.lvlibp) in one project, and I create children in another project.

The Parent PPL ("MoSAIC Addon") is included at the top of the child project.

Whenever I create a VI for OverRide, the created child comes up broken:

The parent is indeed reentrant, the new child is not.

Whose fault is that ?  LV created the child from the parent, why does LV do it wrong and then complain to ME about it ?

If I go to change the properties of the child to Shared Clone - Reentrant, LV asks If I want to make the others the same. 

But the others ARE all the same - I've checked several times.

And it doesn't matter if I choose YES or NO, changing the new child makes everybody happy, until the next time I create one.  It happens every time.

One of us (LV or me) is doeing something stupid.

Which one?

[tst]

---

@CoastalMaineBird wrote:

One of us (LV or me) is doeing something stupid.

Which one?

---

My guess would be LV, with a caveat. My best guess is that there's something wrong with the scripting code, which fails to copy the reentrancy property correctly. I would suggest trying it on another PC to verify that it does work there.

The caveat here would be if you played with the relevant scripting VIs (should be in resource\framework). You might need to repair LV or at least get a clean copy of those VIs from somewhere.

[Darren · Accepted solution]

This is a known bug when creating an override when the parent class is in a packed library, which seems to be the case based on your screenshot. It was reported as CAR 492012, and was fixed in LabVIEW 2015.

[CoastalMaineBird]

OK, thanks Darren.  We're moving to LV 2015 soon.