01-06-2008 03:35 AM - edited 01-06-2008 03:37 AM
altenbach wrote:
(All the other code mentioned does not scale well, and needs to be modified (and gets more complex!) whenever the number of booleans changes. Not good! :))
01-06-2008 04:40 AM
@mikeporter:
"Just debug" is far enough at this point.
Don't you think Joyce could be able to find the mistakes on his own, don't think this could be a better way in learning LabVIEW? Especially in such simple VIs? How did you learn LabVIEW? Did you get explaind everything or have you made your own mistakes, then debugged or searched the help or whatever to find out whats going wrong and have a better understanding of the code you have built?
Sorry but, "I have two different VIs not working the same as they should ..." is not enough ! Learning by doing!
Christian
01-06-2008 12:34 PM
Christian_M wrote: "Just debug" is far enough at this point.
01-06-2008 06:01 PM
01-07-2008 01:44 AM
Guys,
Thanks for your feedback.
But what I tried to figure out is that most people come to forum with questions like: "Here is my VI, why doesn't it work?". And thats not the correct way to get help here or discuss problems. I'm an AE in Germany and in contact with a lot of different customers and applications every day (and their are realy a lot) and I'm also teaching LabVIEW and other NI courses for a long time. Out of this I can say that if you give the newbie LV users immediatly help and correct their issues they will go on with asking for every little problem without learning. That's why I wanted him to debug first, which he didn't!
I think this is enough on this topic. We have different views maybe because we are working with LabVIEW Users in a different way, anyway just go on helping them!
Christian