I will say this. Labview is great for a quick-and-dirty setup or small application. If you need to do anything more complicated, you will find that the entire development environment is incredibly lacking and highly tedious, and there is no meaningful literature on application design in Labview (90% of Labview books are "hurf-a-durf you connect one box to another and it does things, think outside the c++ box man").
As someone who writes VHDL, Verilog, C++, and Matlab on a daily basis, I understand both control flow and data flow programming, Labview is some perverted amalgamation of the two. It lures you in under the guise that you will not need to learn any GUI programming, and then screws you over in anything more than the basics. For example, in a data flow paradigm, pointers have no meaning, as all data is by value. Nearly every complex data type is handled with pointers, and "magical pointer functions" which make life hell, as they do not fit into the paradigm. So then they add "classes", which is a way for them to say that they somehow trump C++ and Java. Upon reading the fine print, one discovers that the class system is similarly FUBAR'd. Then there's the issue of inserting something into code. In a text based language, hit enter, and begin typing. In labview, delete a shit-ton of wires, drag and drop portions of the diagram, put in new bright colored squares, connect even more wires, make everything look readable (see: drag 'n drop ad nausium).
But, if you need a quick and dirty state machine to control something, and you don't mind a polling architecture, I can implement that in about a day...