Inheritance Error？

[yanzhanglin]

Hello everyone：

       When I create Queue_Support Class as farther，then I create UI_Class inherit from Queue_Support Class directly, UI_class works.but when I create Update Loop class,then I click change Inheritance,choose Queue_Support as Update Loop class'farther,Update Loop class doesn't works（create error）.what's the matter?  

       I am very sorry for that my english is very poor.

[yanzhanglin]

it seems that when change Inheritance,Kenerl.VI doesn't update correctly.

[thols · Accepted solution]

Are you on LabVIEW 2020? I found a bug that happens when you change inheritance in LV2020. What happens is that all Call By Parent nodes gets replaced by the actual VI, which results in infinite recursion and out of memory error. This only occurs in LV2020. 

[yanzhanglin]

yes, I use labview2020

how can I deal with this problem,or When will it be fixed

[yanzhanglin]

it means that G# can't be used in lv2020?

[thols · Accepted solution]

No, it means that if you change inheritance in LV2020 using the built-in G#-function, you will need to manually replace all the instances of the changed class' kernel.vi in kernel.vi with the Call by Parent node. Just search for all instances of that VI in that VI and do a replace.

[lsi]

If the COVID19 didn't impact the release schedule, the 2020 SP1 release should be happening anytime soon. Given the severity of this bug, my gut feeling is that it will be fixed within this release.

Cheers

Andrea

[Yamaeda]

---

@thols wrote:

Are you on LabVIEW 2020? I found a bug that happens when you change inheritance in LV2020. What happens is that all Call By Parent nodes gets replaced by the actual VI, which results in infinite recursion and out of memory error. This only occurs in LV2020. 

---

Strange. I wonder what has changed in LV to cause this. We're Calling the standard LVOOP change inheritance i assume?

[thols]

It's not a LabVIEW bug. It's that Call Parent Method was renamed to Call Parent Class Method. This method is excluded from when replacing SubVIs when changing inheritance. So its an easy fix in G#. I have attached an update of the failing VI which shall be put in <LabVIEW 2020>\resource\Framework\Providers\AddQ\G#IDE\support\ScriptingLib.

I just updated to LV2020 f1, but since that did not help with this issue I opened up the G# code and it was pretty simple to find.

To anyone else who wants to contribute, the code is at https://github.com/weaddquality/gsharp

Perhaps there are other places in the G# code which relies on the name of a VI which had its name change with the introduction of interfaces in LabVIEW?

[yanzhanglin]

Does G# update in VIPM？