This still requires several nested structures on the top level together with a case structure that could have MANY cases. Admittedly all this code has to land somewhere, and my aim to to move it out of the top level. When someone looks at that diagram I would like to convey a very high level sense of what sorts of things are going on. And IMHO, putting a bunch of UI update code in the top level doesn't make the picture any clearer. If anything, I think it adds confusion.
LCOD is a beautiful tool to help encapsulate data and functionality, but by itself it doesn't help sterilize the top level (no offense to those offended *grin*).
George
At 01:35 PM 2/26/2004, you wrote:
I hope no one minds me bringing up LCOD again - it just seems like a really good solution here. :)
LCOD (LabVIEW Component Oriented Design as explained in the book "A Software Engineering Approach to LabVIEW") provides a very elegant solution to this problem. Using LCOD one would encapsulate all user interface updates as messages in a component similar to a LV2 style global. This component can then be called ANYWHERE from ANY vi, without using ANY control references! You end up with a nice 'sterile' main vi, without the control reference overhead.
John Howard
