Thanks.
I read in a recent tutorial (that I believe was linked from this site =D ) something I've always tried to do with my programming, and that is do your absolute best not to Design as you Plan.
However, here's my basic assignment right now: Learn LabVIEW by making a program, and adding features that you don't konw what they do and figure it out, thus increasing your experience.
This seems like a highly illogical approach, and that's what brought me looking here. For example, I had been coding a program that moved a "worm" around a waveform graph (graph manipulation, boolean logic, lots of applicable learning experiences), but eventually it started hogging 97% of the available CPU power (and I'm on Dual Pentium 3.0Ghz's!!). I can't find where the resources are being hogged, but I'm not going to waste your guy's time with the VI because, well you've got better things to do than fix my worms. (That's the wieredest thing I've said today...)
However, since I recieved the suggestion of reviewing the examples that came with LabVIEW, and surfing these forums for new and old relavent materials that I can understand/decypher (don't worry, I won't bump old threads ;-p ), I think I'm absorbing the LabJUICE at least twice as fast as I was before, wading through it on my own. =)
Back I go to work the wires
~~ Mule |