Leaderboard

It's getting that damned tatoo that's so tough. Is there an Express VI for that?

Hey, Yair FYI: Steve said:" Nobody knows how to program with 'multiple core'." and Bill:"All the S/W nowadays have to deal with the 'parellel' problem." Regards, Bo

Linked tunnels mean you don't have to keep wiring them through. But even without them, I would never have more than 10 cases (yes. I'm looking at you JGCode...lol) so it wouldn't be a big deal. I also don't generally hop over code. I wire through sub-vis as I like to only have only sub-vis in each case frame rather than raw code - much cleaner and gives you the opportunity to make them subroutines. Locals (and globals for that matter) I try to avoid since you cannot sequence them with error wires. If it doesn't matter about UI updating affecting performance, I prefer to use a property node (because of the error terminal). But that's nothing to do with state-machines But then, I'm me. And that's a bad thing

There is a method of the Pane class called "Unlock Objects" that will programatically unlock controls on the specified Pane. It is a scripting method (so it's exposed in LabVIEW 2010, but not earlier versions). Here is a VI saved in 8.5 that has the method so you can use it. Good luck, -D Unlock Objects Method.vi

(I see that i have posted this in the wrong area... Oh well... one's first post seldom goes swimingly) @Michael: Do you have a link to LAVA CR etiquite? My code is deep in development and has some horrific syntax and improperly named VIs and controls. Is "unreleasable" code ok to release to CR? I assume it is easy enough to "upRev" when available. Some have suggested I Blog about my Lunar Lander antics but I'm not sure it is blog worthy... maybe worthy of a thread here? dunno... I am interested in having my code critiqued but I'm afraid the easy ugly gets in the way. @Yair: Thanks! I saw the asteroids. I've seen that before but now that i have gotten this far i would like to see how they did rotation and colision detection! -TK