asbo

I was around there for the 4th and I don't remember seeing many (any, to be honest). But having driven there, DC doesn't seem a like a friendly habitat for so many Prii

I think that's just a double hard at work

Those are pretty cool - the re-sizable array one is awesome. I really wish the NI probe did that by default.

Hear, hear! Color me jealous. I drive 80% of that in a day.

Just noticed another in the CLN dialog:

Here's a good starting point: http://zone.ni.com/devzone/cda/tut/p/id/7170

I completely respect your driving style. I don't tailgate the crap out of slower drivers, but I do expect slow traffic to yield to fast traffic. The covenant is that if slow drivers going to use the left lane(s) to pass (or cruise), you are paying enough attention to merge out of the lane when it's prudent. I go out of my way to thank drivers that do this. It seems to me that most drivers only ever get negative feedback on the road so I like to let people know when they aren't a thorn in my side.

I appreciate your tendencies to stay out of people's way (especially not nursing the left lane) but people who do pass in the left lane but refuse to match the flow of traffic in that lane frustrate the bejesus out of me. This is what single-handedly turns my 20 minute commute into a 30 minute commute most mornings - I'll duck around a queue and pass some guy going 65 or 70 in the far left lane. I loved driving on the autobahn in Germany, practically everyone was a cognizant, intelligent driver. If a guy was coming up behind you going 300kph, you got the hell out of the way, doesn't matter what you're doing or what speed to you want to be going.

It seems to me this is exactly what I described, with the exception that technically you can still edit the constant value. You can even make the icon small and everything!

These go through my head every single morning. I've literally started writing a document titled "How to not be awful at highway driving" in my head.

Something I've done in the past is to drop the constant value on the block diagram of a new VI, then save the VI as something like "Constant - Spreadsheet Password.vi" and that's that. This does have the downside of requiring one VI per constant, but you could just as well merge all of them with a case structure and a typedef'd enum.

You don't reinstall it *in LabVIEW*, it's a system-wide install. I assume you got an installer from the manufacturer. Use that to uninstall and reinstall the assembly.

Sure, stuff like this happens on occasion. What happens if you turn on Highlight Execution before clicking the Run button?

Another snippet to throw in the ring. It works on all the formats we've come up with so far. I'll try to benchmark this (and the MD5 one) later if I have some time.

Agreed, the alternation character is unnecessary. It'll work just the same, but it changes the logic of the expression (though it may have no performance impact). The Match Pattern node does not support finite quantifiers, but dot and star work as expected. Because string length is an O(1) operation, maybe this is worth considering: Edit: Oops, had a-z as the character range, when it should have been a-f.

Error 7 is: "File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Linux. Verify that the path is correct using the command prompt or file explorer." Try reinstalling your .NET assembly.

The most recent use case I had was working with strings returned from C-based code (e.g., Windows API). There's another thread floating around where a guy was working with data that was NULL padded. All told, I'd probably end up rewriting it by hand before looking for non-printable filter VI.

Whoops, I meant to mention that the patch lordsathish linked for TestStand/LabVIEW 2010 fixed the issue. No new bug here

MSDN has an article on the MessageBox() function in user32.dll: http://msdn.microsoft.com/en-us/library/ms645505(v=vs.85).aspx

Have a look at the LV/TestStand manual, particularly Chapter 4: http://www.ni.com/pdf/manuals/375070a.pdf

TestStand crashes whenever I try to select your test step, but I think your problem is that despite constructing the Local to match the LV type, you didn't actually create a Type for it in TestStand. Click the Create Custom Type button next to the terminal entry in TestStand and it'll walk you through the process.

In a twist of fate, I was just bitten by this when I was pulling in a null-terminated string from a Windows API call. These can probably be combined into a single node using alternation, so your regex would be "^[\00]*|[\00]*$".

When you are replying to a forum topic, you get a nice summary block at the bottom with a bunch of the previous posts. When you reply to a PM, you get nothing. Any way to turn on conversation history below the reply box?

Having read your post before pylb gave an explanation, the concept made sense but I doubt could have explained it as well as he did. That, and I assumed what I was thinking was too simple

Do you mean the TDMS is being committed to disk multiple times per second, or that you use the TDMS Write VI multiple times per second? The latter is completely acceptable if you configure a smart minimum buffer size.