I forgot to mention the issue of message flow design. Within a VI, the signal flow is reasonably self-evident - the block diagram is part of the documentation for the application. In going to Actor programming, LabVIEW doesn't support us any longer - all the messaging is 'wireless' and the description of that design is buried in the numerous state machines. That's why we see the rise in use of UML tools and other applications to document the messaging. Might that feature be brought within LabVIEW to enable automation of that message routing, warning about basic errors and restore self-documentation again?
