Mark Balla

Thats great to hear. If the premium membership came through you should have a banner below your name similar to mine. I'm checking with admin to see if this can be fixed. Please start by posting the current code you are using. Next create a list of the top 3 things you want to add or change. Please try to write as much detail as possible. Then we can discuss further. Mark

Its been said a lot but it can't be said enough. Thankyou for being a part of the LAVA community. Most all have learned something from you over the years. I can think of several times when your post or presentations have made me change how I think about LabVIEW. My hope is that someday you can program in LabVIEW more than you do in C. Looking forward to another 10 years Mark

Certified 8-18-2010 and placed in Right-Click Frame work Category

A Q's LabVIEW Songs at the Bar B Queue can be found here

Since the majority of LAVA members can't go to NI week I thought I would start this topic so those that did go can share some of the things they learned and experienced at NI week. If you have pictures, links or information that you got from NI week please share them for all to see. I have several things to share and I will be posting the AQ (Classes State of the art) video as soon as soon as I can figure out how to get it out of my Droid X. One of the things that sticks out in my mind is during the LAVA Bar B Queue my company donated a gaming mouse to the raffle which I put some stickers on and named it the (Darren Defeater) see image. The idea was that it was something that could help speedup LV programming enough to defeat Darren (the LabVIEW Artisan) in the coding challenge. As it turned out the person that won the prize gave it to Robert the person that actually competed against Darren. He lost of course but seeing my idea come to light made my day. See here for details

The Bar-B-Queue was a blast this year. Great job Justin, crelf, A-Q, Norm. Can someone post AQ's music sheet so all the LAVA members can see it. I can't seem to find mine.

It might help to not think in terms of indicators and controls. I know this idea has been drilled into our heads since we first started working in LabVIEW but X-controls are a different animal. Instead try and think of an X-control items as having 4 states Development time Input mode Development time Output mode Runtime Input mode Runtime Output mode The Facade defines how the x-control with look and act for each state. If we use a numeric control as an example Increment arrows shown, White background, Data entry allowed No increment arrows, Gray background, Data entry allowed Increment arrows shown, White background, Data entry allowed No increment arrows, Gray background, Data entry not allowed So instead of trying to force the numeric controls by hiding and showing them I would instead change a numeric control's properties depending on its current state. Show arrows, Color background white, Enable Hide arrows, color background gray, Enable Show arrows, Color background white, Enable Hide arrows, color background gray, Disable I have found this way of approaching X-control design much less aggravating. Mark

As I have stated for all to read I go to NI Week to meet other LabVIEW developers. So if you are coming to the big show let us know where are you staying, what you will be doing, and what you look like. I have created a MAP that will help new comers navigate Austin. I'm Staying at the Hilton. Sunday: Get in at 4:00pm Ginger Man and ?? (No roller girl bouts scheduled this week but Norm will think of something) Monday: Alliance day Tuesday Lava Bar B Queue Wednesday NI Party Thursday: ?? Here is what I look like (I will be wearing a Tecnova shirt or LAVA Tshirt) If you see me please come say HI but be prepared to talk shop or play fooseball (I need a partner to take on JKI).

The project can be as complex as you want it to be. Make the button cluster as an X-control Have the random number generator only create prime numbers if a user takes more than 1.5 seconds to press the next button then fail the test. Make the buttons alpha numeric. You've been given 3 good Ideas already so you will need to give us more information before we can help you further.

HI Geoff, As far as evaluating it for the CLD he is my take. Functionality: Great no issues Style: Looks Good I would recommend you bundle your data (except the state data) in a single cluster as the Shift Register data. Then unbundled and bundle the data you need in each case. This makes the code more scalable and cleaner. In a few places there are unnecessary bends in wires. (One of the guys I work with lost points because of this) The main program has a default icon. Documentation Needs more comment documentation inside the code. Only documenting the subvis isn't usually enough to get full credit. The buttons need tip strips. Last I knew they want to see tips strips on all the controls on the Front panel. The number one problem that most everyone has when taking the CLD is running out of time. I would recommend you practice your speed programming as well as the items above. If you use Quick drop and a frame work similar to the JKI state machine you should easily be able to build up a flexible state machine in 20 minutes or less. I would like to hear other members take on this also. Good luck on the CLD let us know how it turns out Mark