PaulG.

That dancing baby gives me the creeps as well. But not as much as the Burger King.

I rarely remember my dreams. And when I do it's never about anything "normal".

I'm glad someone is looking out for out tax dollars. Cha ching!

If you don't feel these drivers are at your personal level of satisfaction don't share them with Company A ... or the entire world for that matter on a web page. Hold on to them and improve them if you can. Some day you might be satisfied enough with them to make them public. Then you could send them over to NI's driver network. Company A can get them from NI to post on their web page. Let Company A and NI deal with the legal stuff. My $0.02

I've been a "Team of One" for probably more than 10 of my 11+ years in LV. That's why we come here.

What happens if the disk crashes? IT happens. Have you considered using a dongle instead? They're cheap and very easy to implement.

Indeed. There are few things you can do that are more useful in "self-documenting" code than having well-named data and data clusters along with well-named and well-defined states. If your data is/are named accurately the undbundle and bundle by name help make your code a lot more self-explanatory. However, use with caution. One of the drawbacks to this approach is that in large applications some of your data names can get fairly long. If you have a cluster inside of a cluster inside of another cluster and you go after that data in one of your states your unbundle by name will be so long it takes up half your screen.

I always say: Jack Bauer and I are each others' alter-ego's.

I liked Bugzilla, but haven't used it in a while. And we only tracked bugs with it. I don't see any problem tracking requirements with it. And if you have a traceable document that describes how you track requirements with Bugzilla I don't see any problems with regulated industries, either. Sounds like a plan.

LabVIEW and guns.

I like the idea that the military is paranoid. Really. They get attacked all the time. I'm dating myself here, but my days at NORAD were just a few years before the internet and the only computer security issues we were concerned about were internal - spy vs. spy stuff. Recently the Pentagon was hit with a virus that was delivered and spread via personal thumb drives. I can't imagine working for the DOD now. I'm surprised you are allowed to link to external web sites at all.

Watching this thing run in highlight execution mode made my morning. Nice work.

Sure.

Fortunately I don't need that level of control over my documentation. Usually the customer is keeping everything on file and in order. Good thing. Gateway is almost $2K I've tried printing mulitple VI's but it's cumbersome. I've tried printing "hierarchy" and it gives me fits and errors. So far I've been lucky. Customers seem to be OK with a top-level HTML document of my code. Once in a while someone might ask for a little more detail. I'll leave it at that for now. Everyone has been very helpful. Thanks y'all for your input.

... no interrupts, no distract, XM mode "on", set up travel arrangements to NI Week ...

I agree. I use Darren's "Abort" quite often. It sits on my desktop.

Indeed. There are methods to finishing VI's. But it's not a function. It's a person who goes by the title of "One of My Minions".

WOW! Another lady on LAVA. That makes how many? Maybe three now? Welcome. Don't worry about Norm. He's frequently "misunderstood", but we still love 'em over here.

My company deals with a lot of regulated industries and I frequently need to send my LV application documentation to our customers. Most of the time, along with the Test Specs and Procedures, etc. I send a zipped file with the VI documentation in HTML format. This seems kind of cumbersome, and the "complete" VI documentation does not contain subvi's. Has anyone thought it would be a good idea for NI to provide a "VI Reader" program? It would be similar to software(s) that allow you to read CAD drawings, PDF files, etc. It would not actually send the code itself, but in Print you could create the entire application in "VI Reader" format. My customer would have VI Reader and would be able to look at it without being able to actually edit it. Observation: text programmers have the option of sending source code to anyone in a format anyone can read. This sounds like it might be a lot of work for NI, with limited use, (and I seriously doubt NI would make this available for free ) but before I send this idea over there I would like to get more input. Thanks in advance.

Wow. I just remembered you created that guy years ago. I'm the same way. I don't mind forums and participate in a few. I only signed up for Twitter so I could be a "follower" of a few famous folks I really admire.

I would be careful using the blinking property. I've worked in environments where using a blinking LED was as bad as your team finding out you wear dinosaur pajamas.

Thanks anyway. I do have an iMac. I bought it from my daughter when she bought a new MacBook Pro. It sure looks pretty in my living room ... doing absolutely nothing.

"To be great is to be misunderstood." Ralph Waldo Emerson

? Cash indeed! How many disk drives?! 24? I'm a lowly Test Engineer. Not Bill Gates. But SSD is REALLY COOL. "OMG! It's full of drives!"