Re: Getting Started With Channel Wires

@jkodosky wrote:

>Then the top level VIs could serve as both documentation on how an application is structured and the application itself.

That is the goal!  In fact, it would be great if design could proceed top down as well as bottom up.  Put placeholder actors on the top level diagram and connect them with placeholder channels, so it really is just documentation at that point.  Then open each actor and refine it as a subnet of simpler actors, or as loop containing regular code.  As the actor implementation is fleshed out the channel types get defined and propagate.  The ultimate goal is to make the top level design "documentation" be as easy as drawing on the white board, with the advantage that as it gets refined it becomes the working application.


> have taken time to reply...

Thanks for your interest and enthusiasm!


Question for you: suppose the controls/indicators were on the actor panel as opposed to the top level panel so references didn't have to be passed in, but then there were an easy way to have the actor panel appear in a subpanel of the top level.  Would that be a workable paradigm?


Please give me some time to think about that.


My target audience is often the Basic I and II graduate. I have to be careful not to develop code that is "too complicated" (actual quote from a customer after seeing an Action Engine in the code of one of my associates).


Sub-panels are border line complicated so I have to think about it.


Do have an idea in mind already?


Always curious,



Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos