asbo

That's a relief, I thought there was something wrong with me. I get plenty of flak for using it so much (feel free to chime, hooovahh).

That's awesome! Truly one of my favorite features in LabVIEW, it makes me so much faster. Like most, I came from text-based roots and I'm much, much better at typing than mousing around, which has the perk of not having to learn which function is in which palette.

Interesting suggestion. Just out of curiosity, what makes you think it would be GDI-related? I would think that LV shouldn't need any rendering resources during a build. This could be checked by adding the GDI Objects column to Task Manager, though.

In LV2009 (Win7 SP1 32-bit), it seems that small and very small text do not work. I don't think your code is to blame, I manually cranked it down to 2pt Courier and it didn't change size whatsoever. I think MarkDown support would be pretty cool too, and BBCode and CSS while you're at it!

How much virtual memory do you have allocated? Have you tried reducing the number of VIs cached in memory? Have you tried closing out of literally everything non-essential (Outlook, etc) for the build? How does the memory usage look over time - does it spike or is it gradual?

Is the setup of each of the 5 computers similar/the same? Maybe you have some some 3rd party software or driver that is conflicting somehow. Have you tried creating a new project, dropping your code back in, and then building? Sometimes project files can get mucked up. If that doesn't work, consider reinstalling LV. It's not a great solution, but sometimes it is the fix. Granted, since it doesn't work on 4 other machines, that would be very coincidental.

What version of LV?

I've used both Git and SVN, though most of my experience is with SVN. I like the concept of DCVSes and that was the biggest draw for me to Git. I didn't use it for many binary files, but it worked great for loads of text-based code. On the other hand, I still don't know its terminology and often find myself thinking in terms of SVN jargon. With that in mind, I'm thrilled to see that SVN 1.8 will bring offline commits. I see the power and flexibility of Git, especially in community-based projects, but I think for LabVIEW development in particular SVN 1.8 will be perfect because most of our workflow depends on the lock model, and with offline commits, I don't see much else that Git would bring to the table for binary-based development.

Are you able to manipulate VISA channels in MAX?

Good point. An easy (but still limited) workaround would be to accept a value to pad arrays with. There's no great fix that sticks out to me, maybe something I'll play with later.

Variables are not quite the same concept in LabVIEW as they are in other languages. Read up on the concept of data flow. There's boatloads of other helpful information on that wiki as well. You should post what you have so far in your VI (just attach it to your post) and we'll give you some feedback.

I've seen this before and for some reason I was left with the distinct impression that it did some sort of pre-allocation or maybe passed by-ref. Of course, this is hardly more than weak speculation, and the pre-allocation bit doesn't really make sense with LV's memory management model. I'd love to hear if this is anything more interesting than a no-op.

The maximum file size for FAT32 is actually 4GB so I wouldn't expect that to be the problem (unless some other funky filesystem is being used), but I definitely second the vote for 7zip.

A little while back, I was troubleshooting some code and got hung up on a VI that had the menu bar hidden, so I couldn't open up the block diagram to probe around. It took me a while to hunt down how to do this programmatically (no scripting on my test machine), but I eventually found a post on the NI forums that had the node for me to copy out and use. I'm sure a bunch of you already have a tool like this (or are at least bright enough to find it on your own), but to those who don't yet, enjoy. More than anything, I expect to lose this VI at some point right before I need it again, and now I'll know where to find a copy. BDWin.Open.vi

It took me a whole second to figure out what was going on here. Thank you for that.

Works for me. Either its been fixed or you should try a different browser, perhaps. If the file is significantly less than the expected size (44.7MB), open it up in a text editor and see if you're actually getting a 404 or something like that. If it is the right size, try a different archive utility; I'm using 7zip.

At some point, I remember reading a document that described the 'correct' structure of property files. I don't know if it was in the help or online, but I didn't find what I was thinking of in a quick search. But to answer your question, if you only want to load step limits: <Step Name> Comp Limits.String Limits.High Limits.Low4.13.2.9872 "IgnoreCase" "OK" 4.13.2.9875 "GELE" 672000 661000 should work just fine. TIAS.

As in, 30 images, ever? I would just write enough code to convert them manually and be done with it

Sure - set all your limits to NAN or some other significant value. If you get to the step and that default value isn't replace, the property wasn't loaded. If you set up the property loader to load specific properties (i.e., you don't tick "Load All Properties") then the loader will throw an error if some properties weren't loaded.

Do all of the problematic EXEs use NIDAQmx? Try uninstalling the new version of NIDAQmx and then re-install the LV2009 RTE.

Ahh, I see the distinction. Perhaps some of the overhead is because of the formula node. Try benchmarking an all-native implementation? As was mentioned, LV2010's inline option is advertised as being the same as merging the subVI instead of placing it, so maybe that will end up being a sufficient solution.

I had a desperate hope that the subpanel itself would have a mouseover event, but alas. Have you tried making the child VI set its mouse cursor and see if that has the desired effect?

mod is just a formula, why not code the one that returns the way you want? I think x - (y * int(x/y)) does the trick.

I StumbleUpon'd the snake one. Awesome stuff