crelf

The ASCII characters themselves are the same (eg: 0xF0 on a Windows PC is the same on a Mac), but it's the local representation that's different. I think you should be able to keep evereything in hex representation, so you don't have to deal with the issue?

Oh dear, what have you done?!?

It's a pity that my missus isn't a member of LAVA. Right, and I'm totally enthusiastic to see more of them - in general, custom controls (XControls or otherwise) is an area that's under represented in OpenG IMHO, and I'd love to see what people come up with as submissions.

I think including more XControls in OpenG is a great idea - but I don't think that a separate XControl package is the right way to go: I prefer my XControls to be in the packages that their technologies support (eg: an IP address XControl in a networking package). That said, I'm open to others' ideas...

Wait, what?!?

Only as well as you can taste it Extended into the physical/philosophical world, the idea is the same: armed with the knowledge of only the destination, one cannot know the path of the journey. Therefore, the ends may, or may not, justify the means.

Sorry, I didn't mean editing the existing package, I meant rebuilding it and deprecating the previous. A previous post looked like there would be 2 packges both being supported simultaneously. I think we're all on the same page now.

I think this is one of the biggest steps in recent memory to advance the professionalism of LabVIEW as a programming language: announced today, the LabVIEW software validation tools are now included with the developer suite! This means that anyone who purchases or renews their license for Developer Suite now has access to the following products at no additional charge: LabVIEW VI Analyzer Toolkit, LabVIEW Unit Test Framework, and the LabVIEW Desktop Execution Trace Toolkit. Read more about this announcement here.

Hey Mike - nice hat!

Now that the new version of LAVA is so feature rich, it's easy to see that not everyone has assigned a photo/picture as their avatar! It's doesn't have to be a photo of yourself, just some image that describes you - so go forth and update 'em: let's see how creative you can get

SIlly Pom - have you tried using swype yet?

I actually LOLed when I read that

You wouldn't have to make a totally new package - once the functionality is confirmed in the new version, then you'd just need to update the old package to support the new version, right? Does VIPM allow selection of different versions? Say, 2009 and 2010 only?

Oh dear - that wasn't quite what I was thinking :-) But seriously, this is a pretty good flick (I like Liam Neeson) http://m.imdb.com/title/tt0362269 Ouch :-) That would have been even harder to find had the input consisted of only 2 bytes...

True, except I think he never found a 1 or an eight, right? So I guess it's the sextet that I truly understand. And we have come full circle.

So I'm not a fan of the new color scheme, but I do loved the features of the mobile version of the site! Most of my interaction with LAVA is from the RSS feed, then the site through IE, but now Ki can do almost anything {including admin stuff) on my Droid X2 :-)

What do you mean? I'm talking about the ten degrees on the Kinsey scale - what are you talking about?

Neil was replying to the question if the wire was still broken, not the feature.

Sure - you can save off portions of, or the whole, DAQ configuration in MAX (export to an *.nce file), then reimport it on the new system, either by using the MAX import feature, or programmatically in your LabVIEW code (there's a MAX API under the DAQmx palette somewhere). One relatively unknown feature is that importing *.nce files doesn't (have to) over write all of your MAX settings, so, if you have an architecture that reuqires it, you can load several *.nce files as you progress through your system setup (we use this technique in modular and scalable architectures that are build to run across several different hardware platforms).