crelf

Sounds like "Clean-Up Diagram" should be disabled for diagrams over a certain number of nodes

Get that on the LabVIEW Idea Exchange! Unless it already is, and in that case: link me to it!

We particpate in the Kettering University co-op program - we get students for three months, then the univerisyt gets them for three months, through out their degree (we also support their final thesis). This is good for us (and the student) - it's a longer relationship than an internship, and we also get to groom them as professional engineers (and we then usually hire them when they get out of college). It's a worthwhile program, and we appreciate the oppotunity to put back into the community in this way. Not that internships are bad, co-ops are just a much better fit for our business model. Some of our brightest engineers went to Kettering and matured with us through this program, although our brightest did his co-op at the University of Technology, Sydney.

Personally, I think that the CLAD, CLD and CLA test different things: familiarity with the development environment, ability to develop, ability to architect. It's true that you can do the latter(s) without the knowledge of the former(s) but that doesn't necessarily mean that everything that you're tested on in the CLAD is in the CLD, and the CLD in the CLA. As an example: I've seen ppl who have passed the CLA before the CLAD existed, and I'm not sure they'd pass a CLAD on the first attempt

My mum used to giver me the following advice before school exams:* Answer the question that you're being asked, not the question the you think you're being asked (this was a particular failing of mine).* Give the examiner the answer they want, whether it's right or wrong.Looks like you bombed out on the second one :)Sorry to hear that you didn't make it mate. I know that you're an advanced architect (more advanced than several CLAs that I know), and I think you have 2 options: either challenge it, or take it again and do it their way. I don't know whick of those options will be easier for you.

+1

Now that's a different question - or maybe the same question, but with a different motivation: I agree that we could have more control of the IDE, but we should think carefully about what we want before putting that in front of NI.

Hmmm - good catch. Looks like a coercion bug?

I see what you mean, but they're run-time settings, the BDC is an edit time thing. I'm not saying it's an unreasonable request, but saying that you want to be able to disbale BDC is like saying that you want to disable undo or align right - where does it stop? I think the request might be better phrased as: Wouldn't it be great to be able to undo anything, even after a VI is saved? Sounds like you should temporarily disable that kid

Congrats! ...and welcome to the active poster's club

I'm not going to argue the merits and pitfalls of the Cleanup Block Diagram feature, but I don't think disabling it makes sense. I mean, it's like any other part of the LabVIEW development environment - and it's terribly unfortunate that someone did a BDC and then saved the VI, but that's a two step process driven by the user - I don't think that the development environment should have to handle that use case. You could as easily say that you don't want to be able to save VIs that have had the BDC used on them

Yes, I see the bug too, but I've got to admit that you confused me even futher by swapping the indicators on the FP (double click on your terminals on the BD to see what I mean). I note that if the representation of the numerics in the arrays are different then the bug goes away.

Welcome to the club Seriously though, I think that you'll find this new world quite exciting once you dip your toe in the water. So will all the project be done in C#, or will you be doing a component in LabVIEW? If the latter, I suggest you start with the NI OO Course - it is one of their better courses (originally written by Mike Holmstron of Endevo fame).

NI USB-6210 pinouts are here.

...and the community thanks you for it!

Do you need to have it be a VI front panel? If not, the notifyicon is the way to go - works great.