crelf

The old behavior was prevalent on very old Macs - I don't think I've seen that in any applications (other than LabVIEW) in years

Welcome Davide!

For those who haven't heard of it, asbo's referring to the Code Capture Tool: http://lavag.org/files/file/63-code-capture-tool/ which was coincidentally featured in an NIWeek session I was in a few hours ago

Wait, what?!

Don't forget to follow us on twitter (we're @lavag) for up-to-the-minute updates on goings on and off at NIWeek 2012. And, of course, make sure you come see us at the LAVA / OpenG BBQ on Tuesday. You'll recognize your fellow LAVA members - they're the ones wearing the "LAVA Member" conference ribbons - come to the BBQ and get one for yourself! Have a great time at NIWeek this year - we hope to catch up with you over a beer and some brisket and talk LabVIEW

This could be a neat addition to the NI LabVIEW Idea Exchange. In fact, I'd like to see something the other way around: password protected until a certain date - that would be a neat way to distribute code to the community if you had to lock your diagrams (the best way, of course, is to not password protect it at all ) Also, even if you could trigger a password later, there'd be nothing stopping your user from copying out the code form your diagram into another VI before the time limit expired.

That's what happens when you have a great Texan BBQ organized by a vegetarian! I guess that's the same reason I *shouldn't* own a brewery. *shudder* <- and not in a good way. As if you needed one, but that's another example of how LAVA Mods are freakin' awesome. Just sayin'.

Our friends at WireFlow are donating a awesome Raspberry Pi ( mmmm pi) as a BBQ door prize! The Raspberry Pi is a credit-card sized computer that plugs into your TV and a keyboard. It’s a capable little PC which can be used for many of the things that your desktop PC does, like spreadsheets, word-processing and games. It also plays high-definition video. WireFlow wants to see it being used by kids all over the world to learn programming! Thanks WireFlow! PS: While you're on WireFlow's website, take a look at their cRIO modules for fault injection, resistor emulation and fiber optic communication - totally neat stuff!

An important note to prize sponsors: If you want us to read out a short company blurb about your company when we draw a prize you're donating, please PM jgcode here. If we don't hear from you by Tuesday morning, we'll announce the prize, your LAVA username, and your company's name + url only.

Now you have an excuse to eat popcorn and charge it to your company: LabVIEW Premiere Event 2012! *But only if you're in the US, Canada or Colombia.

http://twitter.com/LabVIEW_BORAT

Ok, that's super awesome right there!

I'll tell you what: you can buy your way into the BBQ with a big ol' bag of NI TShirts!

Congratulations

No problem - that's what LAVA's here for. Now it's your turn to go assist someone else here that needs your assistance. Well, I'd argue the question isn't about being able to afford bringing in external assistance when there's an appreciable risk of loosing all your data - can you imagine the "well why didn't we spend a little more money up front?!?" conversation then?

It sounds like your refnum is the same type between each of the child classes? If so, why not put it in the parent class?

Oh yeah - we "planned" so hard at that bar! I look forward to "planning" more at NIWeek.

FWIW: for those interested in what a HAL is, and an example OO example of one, take a look at this excellent VIShots video.

I just had a great idea: everyone who donates a prize has to keep an extra one aside for me! Brilliant!

As in awe as I am with all of these great prizes, there's one awe-ful flaw to the door prize system: LAVA Administrators and Moderators are exempt from winning prizes. I just thought I'd mention that so, as you gaze in wonderment of all these super cool things that will be given away, you'll remember the more unfortunate people that won't be able to go home with a one. *sigh* Maybe I should resign my administrator position just before the BBQ...

As an administrator of this site, I do not accept this post, and am considering deleting it. aHA! I knew you'd try to pull this one! Read THIS! BAM!

Zazzle is having a sale - TODAY ONLY! Use the coupon code "COUNTRYPRIDE" for 15% off!

I strongly suggest you get a dedicated controller for the mission-critical tasks (think cFP or cRIO) and handle the non-mission critical tasks on the PC (like displaying data, logging to a database or wherever. This means that if the PC goes offline for some reason, the controller continues humming away at what it does best: determinisitc control. Then, you only really need to worry about infrastrucute support (eg: UPS) for the controller - it can continue to control and save data locally while the other system is offline. Also, if you go to the PC to get data off it (I don't expect you're going to run the system completely untouched for a year, right? Not even look at any of the data), doing so won't interupt the process. This is a common option in mission critical systems: we built a similar system a few years ago with 3 parallel controllers (PXI) that could take over from each other within 1ms of a detected failure (those specs are probably overkill for your application, but the technology remains the same). We achevied this using reflected memory (a PXI card with a fiber optic link between them, that all "shared" the same memory) - this worked really well. Another option is to stream reflective memory over a local LAN dedicated to the controllers. I've never been to Amsterdam... The answer to that question depends on just how important that determinism is. If you trust your engineers to make something that won't fail, then maybe do it alone. That said, if they misplace one bit, and the whole thing comes crashing down in the last month of the experiment, you might be cranky An even worse scenario (which I've seem many times) is when it *looks* like everything worked fine, but there's an offset or skew in your data that you don't find out about until you've published - *that* would be a nightmare!