crelf

...or laptop

Sweet - thanks!

Yep - it's not a LabVIEW error per se, it's that you've tried to load a file from explorer (double clicked on a VI, project, etc), and Windows has started to launch LabVIEW to handle the file (you'll notice that your explorer window is still locked). Windows waits for LabVIEW to load to amek sure everything happened smoothly, but after a while it gives up with a couldn't-do-it message (LabVIEW continues to load in the background). That's why a faster PC "fixes" the problem - it just means that LabVIEW's got a better chance to load before Windows gives up on it. Another way to avoid seeing this error is launch LabVIEW first and then open your VI from the File menu. Of course, the other way to get around it is to make LabVIEW load faster, but that's another story

No - not a thong, a "G" String!

Whilst on the topic of NI gear - My old LAVA t-shirt is in need of replacement: I did a search on Cafe Press and found nothing (is that where they used to be)? Can I get other LAVA items as well (mug, cap, underwear...)?

Jim's gone over 500 posts and has been promoted from "Extremely Active" to "<customize this text>" - congratulations Jim!

Great for Sunday roasts when the kids are fighting over who gets the leg...

Sounds like it's Scottish cousin haggis...

I can't say I know any software engineer that is ever excited about documenting code - we usually just wanna write more code

I always figured that was the ultimate sign of becomming mature: buying a lawn mower. Thankfully, I'm not there yet

<Shameless Commercial Plug> There is such a tool available: The VISTA Documentation Manager and Documentation Generator - check out the links on the left side of the page. I have the luxury (and it is a luxury) of working for V I Engineering, so I get to use these tools (and more) internally for free, but even if I worked somewhere else, I would still certainly use these tools. From our website: VI Documentation Manager Quickly edits VI descriptions, controls and indicators. Improves productivity when documenting VI

Forget it - an uninstall and reinstall of DAQmx seems to have solved it (for now...)

I installed LabVIEW 8 on a test PC yesterday as well as a bunch of stuff from the device drivers CDs. I openeed LabVIEW today, and there was no DAQmx palette I manually started the Device Drivers CD installer to try to install DAQmx 8, and it won't let me select it - apparently "This feature is incompatible with products already installed on this computer" Any ideas?

Just finished a mass compile using Jim's tool on a brand new 2GHz PXI controller - 14 minutes and 50 seconds! :thumbup:

If I were you, the first place I'd start would be the NI Developer Zone - there's plenty of examples over there of what you're trying to do, as well as beginner discussion forums.

Why not have them all : +----------+ +-----------------+ +----------+ |XXXXXXXXXX| |XXXXXXXXXXXXXXXXX| |XXXXXXXXXX| |XX.19".XXX| |XXXXXX.24".XXXXXX| |XX.19".XXX| |XXXXXXXXXX| |XXXXXXXXXXXXXXXXX| |XXXXXXXXXX| +----------+ +-----------------+ +----------+

Since you only want the enter key navigation disabled while the user is typing in the string control, use an event structe to detect when the use is typing in the control (key focus), and then set the key navigation of the button to nothing. Then, when the string control looses key focus (another event in your event structure), set the key navigation of the Boolean back to its original state.

It sounds like your constants are type-defs that are set to auto update from their ctl source, and the source is being changed (or at least marked as changed) somewhere else...

Well that's just damn annoying.

Try this to parse out the data from each line: Download File:post-181-1142265391.vi

Nope - still doesn't work on my installation...

Set WhatIsThisSupposedToMean? = True It's great to have you here Ben - you're a constant reminder to engage in a little lateral thinking every now and then. The mind is a muscle - use it, or loose it! Set WhatIsThisSupposedToMean? = False

At the last company I worked at, I did exactly the same thing - I had a standard two-part task that all candidates had to attempt within a time limit on a standard install PC at our office (I had them attempt the task after the interview). It really really helped - anyone can fake a resume, most people can fake an interview, but good ol' Linus is our savior once again: "Talk is cheap, show me the code". It was sobering to find that around 75% of the people that I interviewed who were self-proclaimed LabVIEW genius' weren't able to find anything they needed on the palette, let alone wire them together I always said to candidates: if you need help finding components, or don't quite follow the task, then please ask me - you'd be surprised how many didn't and turned in a couple of VIs with almost nothing in them (and then expected a job )

That's odd - mine don't detatch...

Yeah - I wonder if that guy still had a job at the end of the segment?