Michael Aivaliotis

Hmmm, you guys hang out on the dark side? Admitting that should cost you -1 vote. Hey crelf maybe we should enable negative voting?

Twitter (like most internet traditions) is one of those things that either you get it - and love it - or you don't.

I thought it had something to do with vampires.

Fixed.

I've just updated all the CR authors. I missed a few because I couldn't figure out the member names. If you see anything wrong or if I've missed something let me know.

God that made me laugh out loud!

I noticed the Jing video on the download page. Great idea François. This helps a lot in letting people understand what it does. I think all submission pages should include a small video.

I agree, it should have an underscore. Also, I think capitalizing LAVA is OK.

I think the twitter usage at NIWeek this year will reach an all-time high. With more and more NI folks and LAVA members using twitter, it should be a fun time. Don't forget that LAVA has a twitter account: http://twitter.com/lavag The LAVA team will be using this to post last minute NIWeek goodness. So follow us! Also I suggest everyone update their LAVA profiles with their twitter account names so we can all keep in touch. Who else will be at NIWeek and using twitter? Reply to this thread.

Actually, this is something that I have already given some thought to. Since there haven't been any package submissions to LAVA until now, I hadn't rushed to make a standard. I think the filename should have 'lava' in it. For example lava_lib_rcf_insert_typeconversion-1.0.9-1. What do you think? In addition to the package name, the other issue is installation location. VI Packages that are distributed as being part of LAVA, should be installed under a LAVA sub-palette. At least, that is the goal. Your package is an RCF plugin so this isn't an issue right now. However If you want to setup a template for doing that then that would be a great help to others. I like all the other fields: The only one I have an issue with is the homepage URL. This should point to the main download page of your file on LAVA, not the discussion thread.

It's on the roadmap. It will get done soon!

You can try using a picture control.

And here's a link to information on how to call post-build hook VIs in VIPM: Build Hook VIs

You can also submit it to the VI Scripting code repository.

Yes, you can do that but it's not a good idea to break user expectations of what a radio button represents. Checkboxes would be better in this case.

There's also a link to reply directly to the post.

Oh well. I can't reproduce, anyone else?

The issue is complicated because the answer is what crelf said at the beginning. It's only new LAVA 1.0 threads that someone replies to for the first time. However, on Saturday IPS staff did an update on one of the files that triggered another bug which cause all of the posts to appear "new". So this has started the cycle again. Sorry. Just delete your RSS and start over again, or just mark them all read. This will get ironed out in the long term.

When the VI executes as a subVI, LabVIEW has to put some value on the output indicators. regardless if the indicator is inside or outside the loop, the default values are used anyway right? So I think you have more control of the values if they are outside the loop, then you can place constants to define your outputs in the unused cases.

Just interchange video game console with LabVIEW. We are all fanboys after all...

How about now? I asked IPS to make a change. Before it was putting Pinned topics first, now it isn't. It should be more of what you're asking for. Can you explain a little more? You want a link to today's active topics placed somewhere else? Where exactly? A screenshot would help.

I didn't even get a reputation vote for that? What a tough crowd!

Back to top is back.

One problem that you will have to address is how to synchronize the multiple test execs. Also, how do you effectively manage your hardware (test equipment) allocation among test execs. I would seriously consider Teststand as well. You can reuse most if not all your test code written in LabVIEW.