crelf

Admins and moderators don't read every post - in future, if you want something like that done, you need to report it to a moderator (using the button).

Kudos on the package Jon - now I can deprecate our internal reuse package: and that makes me very happy

Ha! I can't argue with that Right - and, in my opinion, one hurdle that's relatively easy to overcome, yet trips up so many people, is nomenclature. Classes, objects, encapsulation, inhereitance, methods, properties, singletons, etc <- these words might be forgien to someone starting to work with OO, but they're usually just names of something they already know (and have probably even used!), but it's just takes some time to get your mind around them.

Congratulations to the incoming freshman class of LabVIEW Champions! Once a year, new members are inducted into the Champions programme, and this year's 9 new members represent a high calibre group of individuals from all over the world. I'm also proud that many of the Champions (if not all?) are leading members of the LAVA, and have shaped, and are shaped, by our community. Congratulations!

Oh yeah - it's soooo pretty to watch

Sorry, I can see how you read that, but I wasn't trying to say that OO is anti-dataflow, just that anything non-OO is, well, non-OO

At least you already learned it, in a more classical sense. It's usually quite a task to "get" OO when you've only been working with (relatively) strict dataflow most of your life. I remember the simultaneous look of wonderment, confusion and disgust on my students' faces when I used to teach the Endevo GOOP course.

I guess it depends on what you want to do. We use custom xsl stylesheets a lot with ATML reports, and occasionally have to nip into the data to make mods (which, as suggested by others, we do with .Net - we've built up a reuse library of such functions that wrap the .Net stuff, and is compatible with the LabVIEW vi.lib functions).

Text programming is stoopid.

Maybe I don't understand your question, but, if your project needs to use a PCI slot in your application, buy a PC with at least 1 PCI slot. If your project needs to use a serial port, buy a PC with at least 1 serial port. etc...

Note: although I'm an admin here at LAVA, my posts do not necessarily represent LAVA. I think the wikipedia blackout page puts it best: IMO, replace "wikipedia" with "LAVA", "wikipedians" with "LAVAites" and "encyclopedia" with "independant LabVIEW community", and that pretty much sums it up. I can't think how it would be possible for LAVA to continue to exist without being open to litigation for the site, it's admins, moderators, and members.

http://thingsboganslike.com/

I think the idea still has merit, and adding the Boolean suggested would keep everyone happy - I think you should still push for this if you think it's valuable.

I don't think this is a good idea - there are only a few cases where I would expect a subVI or primative to ignore an error in: closing references comes to mind. I think that changing the behaviour of common reuse components in this way is untintuative. If we really want to do this, I'd suggest that the OpenG VI include an "Ignore incomming errors" Boolean input (kind of like how you can ignore node errors on property and invoke nodes).

Nah - I don't know the guy who suggested that, but he looks like a real bogan.

Baahahaha! I'm thinking less superhero, more Halloween cowboy costume. http://qkme.me/35oxy4

I'm not generally a big fan of memes, but this one drew my attention recently: it's a picture of our very own Justin Goeres as a mentor in the 2011 FIRST Championships. Go ahead and add your own caption(s) - I look forward to seeing what LAVA members come up with.

IMHO that's the best kind of excitement - congrats on the new tack.

Norm's tool looks pretty good, but I think it only works at edit time.

This is actually one of my favorite new 2011 features

We all love using LabVIEW, but here's a new year opportunity to help give something back: http://labviewjournal.com/2011/12/help-with-labview-research-project/ All they want is a little code and a few minutes of your time.

Learning with your friends - that's a neat concept!

Here's an existing colleciton of CRC functions: http://forums.ni.com/t5/LabVIEW/Checksum-calculation/td-p/86249

You don't really comment all of your code to that granular level, right Jim? I mean, it almost looks like you're trying to embed your design document in your code

The continued successes and growth of LAVA and the community it supports is based soley on our members - so all our thanks go to you guys! Thanks to everyone who got involved in 2011 Here's looking to an even better 2012!