Greetings, all!
LabVIEW 2020 brought us interfaces, which have very exciting implications for how we will build systems in Actor Framework. Sadly, a couple of bugs in the AF Project Provider made it very difficult to actually start using interfaces.
This unofficial patch resolves the following issues:
1. The project provider does not recognize actors that implement interfaces as actors, so users cannot access the provider tools.
2. Message rescripting does not work on interface messages.
Installing the Patch
The attached zip file contains three VIs. Simply copy them from the zip file to the appropriate folders in your LabVIEW folder.
This is an unofficial patch, offered as-is and without warranty. We strongly recommend you make backup copies of the files you are about to replace, and that you install the official patch when it becomes available.
Place these VIs in ..\vi.lib\Utility\LVClass:
Read Class Ancestry Without Loading.vi
Is Class Not Interface Without Loading.vi
Place this VI in ..\resource\Framework\Providers\MessageRescripter\Support:
Find Target Actor.vi
You will need to restart LabVIEW for the changes to take effect.
Please comment here if you encounter any issues with the patch.
About the "unofficial" designation: https://forums.ni.com/t5/Actor-Framework-Discussions/Message-Rescripting-Broken-in-Interfaces/m-p/40...
AristosQueue, in another post, said this: "'Unofficial' only in the sense that it isn't NI published. But Allen and I have both vetted each other's work on this... he was the one with the bandwidth today to actually publish it! But these are the fixes that will eventually be in a patch for LabVIEW 2020."
As reported in this thread, the patch for #1 is not working for me. The fix for #2 works great though! Thanks!
I just tested the patch on a VM with a clean LV 2020 install, and confirmed that the patch zip is correct. DM me with the details of your current behavior. (I am OOO tomorrow through Sunday, so my response won't be prompt, but I'll look into it as soon as I can.)
Has this officially been patched in LabVIEW 2020?
The fix was included in 2020 SP1.