Well I don't know about you guys, but I'm finding it increasingly difficult to keep up with all the new improvements in LabVIEW.
1) I find the best method is to attend a seminar presented by a LabVIEW expert/ NI who actually shows you how all the new features work, shortcuts, tips, things to watch out for etc.. I can learn more in a two hour lecture than spending days on trying to learn it myself and because they are free they are very cost effective
2) Training Sessions (NI / Third Party) are also very effective, but they don't seem to cater for the person who has good knowledge of LabVIEW, but is no expert and wants to learn all the tricks for good large scale development software. They also tend to be fairly expensive, but are worth the money in the long term.
3) Some of NI's video tutorial's and web events also give you a good audio/visual description, but they tend to be fairly basic.
4) After that it's basically scouring the Example VI's, Developer Zone, infolabview, Open G and LAVA (not necessarily in that order) to get some idea of how a concept works.
Back Ground first. I started with Labview 3.1 and I am using 6.1 now. I have tried 7.1 and 8. I hate both of them. Quit changing the interface MICROSOFT!!! I have a 21" screen and still don't have enough real estate. Get rid of the giant icons... If you need it that simple(which never works for me) sell it in a different product, leave Labview alone.
I have to agree, the Help is Lame. And when you dig deeper into help you get another lame (short) discription of what a function does. Inverably there won't be an example for it either.
What got me going in the begining in Labview what the example programs. Also, that was the best thing about borland C. If I wan't to know what a function does there is an example I can cut and paste in my code.
So, I would like to see more function and more examples and more discription in the help. CTRL H. Leave the interface alone, I don't want it, and I am not using it. It's only a bunch of Fluff and not much more usable code.
I think you are trying to please the Newbe's over the Oldbe's, Us Oldbe,s just might say screw it and go back to Microsoft.
Ok, I feel better now.
Message Edited by shoneill on 02-28-2006 02:58 PM
error handling in labview is so easy that a good example seems to fail
Always wire an error in and error out and inside check for error and skip if an error is already present.
You never want to mask the first real error.
If you have parallel error wires use merge error (still looking for a way to gather all errors) but the most important one has to be in error out.
That is all to make error handling work, but the finer details are for chapter 2