Michael Aivaliotis

See here: http://decibel.ni.com/content/groups/labview-add-on-dev-center/blog/2010/06/03/accepting-submissions-for-niweek-2010-award-labview-add-on-of-the-year-deadline-july-9th

This issue is now resolved.

We are currently running 3.0.5.

We upgraded the site and this got changed. I'll try to get the author info back. You are correct that now only new topics are posted to the RSS. I'm trying this for a while. How do you like it? Isn't it better than getting the entire thread posted every time? No more RSS bombs.

http://alfastring.tk/

Yes, Known Issue:

The old LAVA site used the Google Custom search embedded in the site. There are good things and bad things about it. It's unfortunate that the built in search sucks.

This issue should be fixed now. Guests should be able to download previous versions now.

I'll look into this. The intent is to be able to download stuff in CR whether you are logged in or not.

I just got a notification from IPB (the makers of the LAVA site script engine) that there is a new version of The downloads script (Code Repository) currently in Beta. There are some new things in there. Here's an excerpt of their announcement which indicates the most usefull features in my opinion: Having multiple files is great. Now we can have files for various LabVIEW versions or even one zipped *.zip version and a packaged version *.vip.

We've created a special Quick drop plugins category. And yours is the first in there.

All. Let's keep this conversation civilized please. The Earth's been here for millions of years and it will still be here for millions more, even after we've become extinct. So at least, for the short amount of time we have, let's try to give each other some respect.

I'm not a fan of substates or nested states. I've gone down that road many years ago and came to the conclusion that it's simply too hard to work with. It makes the code harder to trace and debug. I had a colleague that swore by that technique. I hated working on his code. If the code on the diagram is so complex that you need to break it down into nested states then I would consider using more subVIs instead. Makes the code easier to work with and debug.

crelf, I don't think the crowd here on LAVA have the programming skills to write any interesting games in LabVIEW.

Are you just trying to bait me? Hmm, I guess it worked.

Can you attach a screenshot of what you see to this thread or in a PM please?

Well, it's actually still the same VM. It's not multiple VMs. This is just how VMWare operates. The branches or snapshots are rooted to the same VM. I'm not suggesting you copy or clone the VM, thus creating multiple VMs. In any case. Even if it turns out that this is a violation, I still have a fallback since our company has an Alliance member site license so I'm still good. However, in other cases I can't see why this would be a problem.

This is normal behavour and is related to LabVIEW not Vista. In your browse options you have selected "new or existing file" correct? Change it to "Existing File".

As far as the LabVIEW licensing. What issue are you guys trying to solve here? Do you want to run multiple labview versions, each one on a different VM? Or the same LabVIEW version on multiple VMs? If it's the latter, same LabVIEW version on multiple VMs, the solution is simple as I see it. I use VMWare. I can create one VM and then I can install whatever I need on it including LabVIEW. I then register LabVIEW. From there I can use this "virgin" VM and then I can create branches, snapshots etc. I'm still running it on the same machine but I only really need to register LV once. Then when I need to work on a new project I create a branch from this Virgin VM. It's still essentially the same machine so there's no license issue. It's analogous to backing up your physical machine and restoring from scratch every time.

I've done the multiple LV versions and various OSs. Currently running Vista with 8.2, 8.5 and 2009. You should have no problems installing this stuff in any order. The clincher is the drivers. So basically, in the installer of each version un-select the choice to install drivers, you don't want to do that at all. One of the problems is that the driver install searches through your system to see which version of LV you have installed and installs driver support for those versions. So what you want to do is install all your LV versions without driver support and then download the latest platform driver file from the NI site and do a final driver install. Keep in mind that this will get all your LV versions using the latest drivers. This is unavoidable. So if you have a 7.1 project that requires year 2008 drivers then you are screwed. So what do you do if you need 7.1 to use older drivers? Virtual machines! They are a godsend and the only real way to support old projects that must use old drivers. Anything else is just an exercise in futility with lots of hair pulling.

I'm ROFL right now.

For a list of known issues in LabVIEW 2009: LabVIEW 2009 Known Issues

Hmm, not sure what happened to this one. We're looking into it. Sorry.

Why does LabVIEW 2009 have to convert toolkits on startup and why does it take forever. You'd think that after the first time, the toolkits don't need to be converted again.

'suspend when called' has been there since the early days of LabVIEW. http://zone.ni.com/devzone/cda/tut/p/id/4141