asbo

Hahaha, I came off way more green than I meant to: specifically with a string, how do the modes differ?

Does anyone know a definition for the behavior of using the equal comparator with strings in aggregate mode? I couldn't find any circumstance where it produced a different output than when in elements mode.

It's an on-going issue.

You should share your solution in case someone else comes across this thread with the same issue.

I don't think this is a problem with hot-linking so much as LAVA's software trying (stupidly) to authorize image URLs only by extension - I don't think it looks at MIME-type at all because in a browser I show "image/jpeg" and we certainly can embed JPEGs.

What's worse is that you're laying through two different ActiveX automations - the one for Google Earth, and then the web browser one. You might look into finding a way to implement the Google Earth ActiveX directly.

Agreed.

That's just not right. NI, we demand more exposure of your pizzles.

Excellent, thanks!

I started writing this post as a question, but found the answer by the time I was done, so I thought I'd make it informative. TortoiseSVN (and probably most other SCC software) will allow you to override the default diff-viewer per file extension or MIME-type, so I was looking for a way to do this is TestStand sequences. I found this snippet in the TestStand help file: So I plugged in a custom viewer for .seq using the path "C:\Program Files\National Instruments\TestStand 4.2\Bin\SequenceFileDiffer.exe" %base %mine. You'll notice this is a little different than prescribed by the help file - first' date=' the executable name is different and second, there are no quotes around the parameters. For whatever reason, putting quotes around the params broke the paths. Even without quotes, though, it works with fairly long paths (135+ characters) which has spaces in it. Another plus, IMO, is the diff that pops up isn't the whole sequence editor - just the pane that shows the diff results. P.S. If you didn't know, TSVN ships with support for diff'ing a whole bunch of MSOffice formats - really handy for comparing documentation revisions! For the truly lazy, here's a registry file to add the diff for you. Take note, I'm using TestStand 4.2! You'll have to rename it to .reg to merge it. TortoiseSVN Diff - seq.txt

Necromancing this "tread" Tanner, did you ever find a satisfactory solution? Did you abandon git altogether?

I already made a post about this in the site/support sub-forum.

That would lead me to believe it's a problem with your buddy's machine, not LabVIEW. By identical, I meant operating system, hardware, etc.

Found this little gem. Sweet product promotion, NI

Are your machines otherwise identical? The crash may not be LabVIEW's fault.

Why would you expect row height to adjust to the -length- of your content? I would expect a column autofit to do that. This would be easier to troubleshoot if you uploaded your actual code and a sample spreadsheet. In any event, you probably can't autofit a collection of rows all at once. You'll have to iterate through the rows you care about (UsedRange might be useful for this) and then do an autofit on that. Conversely, you can select the cell you want autofit (Range("B2","B2")), get the EntireRow and EntireColumn property and run the autofit method of that. I just noticed that your description field is actual a merged cell; not sure how much that will complicate things.

BD Cleanup gave it its best shot ... (the raw bitmap was 28.8MB and this PNG is 1.1MB)

That's the format of a string which can be passed right into Windows API for a common Open/Close/Save dialog (anyone who's used Visual Basic or CMNDLG32.DLL should recognize it), so it won't be changing anytime soon. I only presume that NI works some magic in the background to ensure cross-platform compatibility, but I have no particular experience myself.

Using ActiveX automation, you could command that row/column to autofit. If you're not familiar with Excel ActiveX automation, search around LAVA a bit; there's been a few threads about it. As for alternatives, you might consider generating an HTML report instead.

Touché. For whatever reason, I had it in my head that it was a VI - great point.

That really shouldn't change whether or not the VI itself is reentrant, though.

A couple (at least) of these have sprung up, for no apparently reason. If you click them, the light-box version is sized normally. (Win7 x86, FF 3.6.3)

Just a sidenote, even if you remove the "All Files" selector, a user can still display all files by typing "*.*" into the field and pressing Enter (on Windows, anyway).

Are we any closer to a decision on this? My productivity is skyrocketing, and, frankly, I'm quite disturbed by it.

NI maintains a list of known issues for many of its products. Can't comment on the 8.2->2009 growing pains, though.