04-13-2021 04:48 PM
When you create a static dispatch property node accessor VI with regular non-GDS classes (i.e. using the native class editor features in LabVIEW), the new property VI is marked as Inline. The same does not happen when creating a static dispatch property node accessor VI with OpenGDS. It is created as a non-reentrant, non-inlined VI. From what I can tell this is because the property node accessor VI template is set to non-inlined to support being dynamic dispatch.
To solve the issue for static dispatch property node accessor VIs, I propose a fix to the following VI:
[LabVIEW 20xx]\resource\Framework\Providers\Open_GDS\ClassProviders\Provider_LvNativeClass\ClassWriterNative_class\CreateMethod.vi
I made the following edit to the VI, and now my static property node accessor VIs are marked as inline when they are created:
I assume a similar fix would need to be made to scripting for other class types (GOOP3, GOOP4, etc.), but I didn't dig into their scripting code so I wasn't sure.
Solved! Go to Solution.
04-14-2021 08:53 PM
(cross-posted to the OpenGDS issues list here: https://github.com/opengds/OpenGDS/issues/64 )
04-15-2021 03:11 AM
Thanks,
I'll add that right away.
BTW, I saw on twitter that you liked the new 2020 Class Creation dialog that now saves the class to disk as well :-).
The latest OpenGDS 2020 version does a quite more steps for you 😉
05-10-2021 07:33 PM
Available in the latest version:
OpenGDS 1.2.59(LV2020) LV2020-32
OpenGDS 1.2.59(LV2020) LV2020-64
Please keep reporting bugs here:
https://github.com/opengds/OpenGDS/issues
02-01-2022 04:37 PM
Fixed this again, since there could be a race condition is the previous solution.
This fix will be in build 1.2.74