I was playing around with Interfaces in LabVIEW 2020 and noticed that whenever I try to rescript an AF message in an Interface, I get this message:
Is this already a known issue and is a fix already in the works?
Solved! Go to Solution.
We know about it, and we know what part of the code needs to be fixed. I don't know if a CAR has been filed, and I can't speak for when NI will publish an official fix, but I'll try to post an unofficial correction in the next couple of weeks.
I'm wondering if this is related to the problem I found with how the message maker recognizes classes as actors. If an interface is alphabetically prior to the parent actor class, the message maker doesn't recognize the actor as being an actor.
Sorry to keep pestering, but this issue as well as the disappearing AF menu are making it a lot more difficult than it needs to be to adopt interfaces. One of the projects I'm working on is very large and would see huge benefits from incorporating interfaces, but without these two scripting utilities, there's some reluctance to use them.
Any sort of update as to if a fix might be released in a patch (great!) or would we have to wait until SP1 (tougher sell to management) or even 2021 (please no - might be a deal breaker).
I'm in the same situation. Interfaces seem like a much better implementation for the actor framework application I'm working on, but it's tough to tell the less experienced developers on my team to manually create all of their message classes. Or to instruct them to go through some process of removing interface inheritance from their class, then scripting up their messages, then re-add the interface inheritance afterwards... I'd be happy to have an official or unofficial fix for this. Thanks!
Adding to the chorus. For folks using Actor Framework in large projects, interfaces add massive value for decoupling and simplifying messaging. But especially for those of us using large AF projects with team members with a range of skill levels, scripting is a prerequisite for adoption.