Jim Kring

Here is a bug that I've noticed in LabVIEW 8.0.1. Download File:post-17-1146793345.vi

This would only be possible by first comparing Microsoft to Nazis, which means that you would have to invoke Godwin's Law on yourself, which means that you automatically lose the argument. It makes for quite a paradox. I suggest that we simply offer to buy AMSLLC a beer and debate the issue at NI Week ...mmmm.... beer. :beer:

The existence of that resource is just one example of something that one learns while preparing to take the certification exams Doesn't it makes you wonder what else you might not know? As Einstein said (I am paraphrasing), "As the radius of the circle of light increase, so does the circumference of darkness surrounding it."

Irene, no, I was not trying to single you out. Notice that I switched from "she/her" to "he/him" in my second paragraph. I'm just an equal opportunity kind of guy

I probably understand more about your perspective than you give me credit. -Jim (James) Kring James Kring, Inc.

NI Certification is an important milestone on the path to LabVIEW enlightenment (which is more of a journey than a destination). If someone thinks she's good at LabVIEW and she hasn't taken any courses or obtained NI certification, then chances are she's not as good as she think's she is and she probably doesn't have the experience that our organization is looking for. (I'm also responsible for hiring LabVIEW developers.) A certification requirement for hiring certainly makes for a good filtering criterion (and you can't have too many). At our organization, we require that every LabVIEW developer be on a professional path to become a Certified LabVIEW Architect. Bottom line, certification is an absolute must for anyone serious about calling himself a LabVIEW expert -- if only to understand the process and expose him to a variety of concepts. Certainly, I gained a lot by obtaining my certification (I am a CLA, and have previously held my instructor certification) -- I learned about areas of LabVIEW that I was weak in, and I subsequently strengthened those areas. Cheers, PS - please don't compare LabVIEW to IT (I can say this without getting in trouble because our company doesn't have an IT dept.)

Try using the MSI Installer Builder from OpenG. This will allow you to build an installer in LabVIEW 7.1 from anything.. yes, anything.

That's a five star reply!

I have found another variant of this bug. Download File:post-17-1145600287.vi

How about Beer's Law?

Some of you may have heard of Godwin's Law. I think there should be an inverse law, which dictates that whenever the discussion degenerates to a discussion of beer, the topic is officially closed to all discussions other than beer, the person who brought up beer is declared the winner, and we all toast to them.

That reminds me of a time where I spent the whole day curled up on a couch in the convention center. Somehow, the night before, I switched from drinking beer to long island iced tea... bad idea. BTW, a wise man once shared this secret with me: if you alternate between beer and water (1-for-1) you can last all night and wake up refreshed in the morning.

Maybe LabVIEW's feature set is definining what users typically do with LabVIEW. Unnecessary coupling that is the product of legacy will only help you hold on to the past and keep you from moving forward.

Be careful, Chris. This is what happens after an evening of drinking with Mike at The Gingerman. Next thing you know, you'll be famous.

I would highly recommend not using LabVIEW's support for SCC API. It is a real pain to use, since it assumes a single repository per LabVIEW installation. Unfortunately, this only reflects reality for the LabVIEW R&D team at NI . For those of us on the outside, we typically have different repositories for each project, not to mention the possibility of different repository types (CVS, SVN, ClearCase, VSS) for each project.

> Does anyone know how to alter this? Or should this be on the bug list?? No, it cannot be altered. It is a feature, not a bug.

> So - if you are forced by an organizational restriction to use VSS on the server side, then SoS is an excellent option. ...or you can find an organization that strives to use the very best tools and is continuously improving its process.

> I guess the one big issue we're having with the CVS and why we just haven't made the switch is so far, our IT guy has not been able to get it up and running so we can try it. Though we've all been so swamped lately we really haven't had time to try and work the issues out. Sounds like organizational/cultural issues, not SCC issues . Also, if people like VSS, there are a variety of GUI's that have a VSS-like feel (explorer-style interface). Personally, I like SmartSVN (which is also cross-platform/Java). But for windows, there's no contest that TortoiseSVN is the best.

Now's a great time to try to convince them to use subversion Anything's better than VSS (not always, but you know what I mean).

I am invoking Godwin's Law. This topic is now closed. Sorry, alpha, you lose again.

No, but there is a website: Conspiracy Theories for Dummies.

What about the law books?

No, I don't think so.

How do you change a VI from Run Mode to Edit Mode (and vice versa)? You know, the way you can using Operate>>Change to Run (Edit) Mode (<ctrl-M>). I can't seem to find any way to do this. P.S. - The Edit Mode on Open property is not what I'm looking for -- I want to change the mode immediately.