Jim,
Thanks for the reply. I'm certain that it is the small project aspect of what I do that has enabled me to get by with less than an optimal technique. Generally, I am going it alone. However, I would like to leave a legacy of readable, maintainable code, by anyone minimally trained in the art.
This has actually led me to avoid the use of "the latest and greatest" functionality available. On the other hand, I dont want to be crippled should I come across code where someone used all the latest stuff; I look at it and realize I have no idea what's going on.
So to all the advanced LabVIEW programmers out there, what's the next step, generally, past the "state machine" in general program archetecture? Can anyone say "well, I'd make use of notifiers, then semaphores, then rendevous and I think the value of "first time run?" is obvious" this might help me with the next set of specific LabVIEW functions to study.
As far as the Object Oriented stuff, at this point I dont know the difference between a Function and a Life-Cycle. I'm sure I could guess by analogy, but my question was more directed at the specific "Advanced" functions provided by NI on the Functions palette, relative to programming methodology. If these are the elements that allow OOP and you have to know or have studied OOP to be able to grasp what they do conceptually, knowing that would help me too.
Best Regards,