LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

"New VI for OverRide" creates broken VI

Solved!
Go to solution

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:

 

Broken.PNG

 

 

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?

Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com


LinkedIn

Blog for (mostly LabVIEW) programmers: Tips And Tricks

0 Kudos
Message 1 of 4
(3,416 Views)

@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.


___________________
Try to take over the world!
0 Kudos
Message 2 of 4
(3,392 Views)
Solution
Accepted by CoastalMaineBird

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.

0 Kudos
Message 3 of 4
(3,382 Views)

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

Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com


LinkedIn

Blog for (mostly LabVIEW) programmers: Tips And Tricks

0 Kudos
Message 4 of 4
(3,377 Views)