05-05-2014 10:55 AM
drjdpowell wrote:
Beter yet would have it function like Call by Reference; drag and drop in the VI you want to call inside the Actor and wire up the inputs (actor and error inputs would be greyed out). Job done. Any message class needed would be autogenerated and never seen at all.
Not quite a slam dunk "better yet"... I have many messages that are not one-to-one mappings to actor methods. But certainly we could move in that direction.
Alas, all of that requires some substantial language changes, and the topic at hand is what to do for 2015 to improve the iconography of the classes as generated. So the halo is a tangent.
05-05-2014 11:10 AM
AristosQueue wrote:
Not quite a slam dunk "better yet"... I have many messages that are not one-to-one mappings to actor methods.
Ah, but that's why I said "VI", not "method". Have it accept any VI with standard "actor" and "error" inputs/outputs. Doesn't have to be in the actor's class.
Alas, all of that requires some substantial language changes,...
Unfortunately, yes, but such a feature would be of substantial benefit.
05-05-2014 11:36 AM
Ah, I see. It was the phrase "inside the Actor" that had me tracking differently.
And now, really, back to the main topic. 😉