crelf

When I'm in a deeply creative mood, I can't go past the 1985 Dire Straits classic Brothers in Arms.

QUOTE (PaulG. @ Aug 11 2008, 07:47 PM) That's just plain wrong! Later that night... Ah crap! Now I've got "Tie a Yellow Ribbon 'Round the Old Oak Tree" in my head!

LabVIEW does not currently support IPv6 protocol and probably won't in at least the next version (from what I've been told). I had a need to create a LabVIEW IPv6 compliant client for a current project so I created this set of functions (Open, Close, Read, Write) necessary for client-side connectivity. I did not need and have not written any server side functions (Create Listener, Wait on Listener, etc.). These functions mirror the native LabVIEW functions as closely as practical and can serve as drop in replacements (they also support IPv4). These functions use the .NET System.Net.Sockets namespace and .NET2.0 so they are windows-only. They have been tested on XP but not on Vista. The zip file includes the LabVIEW function VIs, a demonstration VI created from the Data Client.vi from the \LabVIEW 8.x\examples\comm\TCP.llb, and the Visual Studio 2005 project used to create the .NET DLL used by the LabVIEW functions. The Data Client Example uses IPv4 since it connects to the LabVIEW Data Server (which only supports IPv4) Submitter: mesmith File Version: 1.0.0 LabVIEW Version: 8.5.x License: Creative Commons Attribution 2.5 License Admin Note: this LAVAcr submission has been moved from the submission queue to the Code Repository In-Development area due to inactivity timeout.

Description: This toolkit will scan the active project for any SCC anomalies in the following categories: - Files not in SCC - Files not up to date (a newer version exists in SCC) - Files not checked in Additionally it checks if the following two things: - Files are located under the lvproject folder - Files that are in the dependency list but not under the LabVIEW executable folder This toolkit uses the LabVIEW built in SCC VIs. Instructions: Unzip to a custom location, or install the OGP using VIPM (www.jkisoft.com/vipm). To use the toolkit you have to call it from the menu of a LabVIEW window. Submitter: Ton File Version: 1.7.3 LabVIEW Version: 8.5.x License: The BSD License Admin Note: this LAVAcr submission has been moved from the submission queue to the Code Repository In-Development area due to inactivity timeout.

LabVIEWSearch.com works fine on my PC - are you sure you don't already have some zombieware on your PC that's intercepting the page?

QUOTE (ASTDan @ Aug 10 2008, 04:36 PM) There are a lot of options, and it really depends on your needs: what is/are your intended use case(s)?

QUOTE (jlokanis @ Aug 9 2008, 12:48 AM) I agree that submitting suggestions to NI about more appropriate room assignments is definately the way to go in the future, but I don't think NI necessarily did it on purpose - we just need to let them know what we want. For example, Omar and Jim's talk on software reuse managment was in one of the biggest rooms. That said, it was still overflowing with lots of people standing and other sitting on the floor - maybe next time it needs to be part of one of the keynotes

QUOTE (Norm Kirchner @ Aug 8 2008, 07:43 PM) I agree - the first step is to admit that you have a problem. ...it's your choice of beer that's the problem

QUOTE (Val Brown @ Aug 8 2008, 05:21 PM) Hopefully NI will also get the idea by correlating the number of seats in the rooms and the number of people's barcodes scanned as they entered the rooms. I know there were a number of sessions I was in with a lot of folks sitting on the floor. One presenter almost tripped over someone in one of the sessions...

QUOTE (jlokanis @ Aug 8 2008, 02:30 PM) Old dog here too (LabVIEW 3) - but I can't live without the autotool now. Originally, I hated it, but a http://forums.lavag.org/PeterB-m1272.html' target="_blank">talented colleague whom I respect very much suggested I learn some choice keyboard shortcuts and just persevere with the pain for two weeks, and, sure enough, now it's second nature.

QUOTE (b_subhasis @ Aug 8 2008, 04:28 AM) Off-topic (only a little ) - what "metrics in LabVIEW" are you talking about? http://forums.lavag.org/Node-count-versus-SLOC-t3632.html' target="_blank">Nodes or GOBs?

QUOTE (jed @ Aug 7 2008, 11:51 PM) I saw Jed and Jake at the Austin airport this morning and, while I saw a little levity in his situation (mostly because I wasn't in it ), they were *not* amused...

For those of still left here in Austin, desperately trying to get over last night's hangover, there's a handful of us getting together at Stubbs BBQ tonight to eat, drink and listen to Nellie McKay (she's a fusion of smooth jazz and comedian by the look of her website). Arrive for dirnks/food after 6:30pm, show starts at 9pm. Stubbs BBQ is within walking distance of the Austin Convention Center: 801 Red River, Austin ph: 512 480 8341 View Larger Map

QUOTE (pallen @ Aug 6 2008, 10:33 AM) Rock on dude!

QUOTE (mross @ Aug 6 2008, 07:55 AM) No worries In fact, using DAQmx with E-Series boards exposes some of the functionality in the boards that we couldn't get to with traditional DAQ. I'm grateful that NI spent the time and money to invest in developing DAQmx during the slowdown a few years ago :thumbup:

QUOTE (mross @ Aug 5 2008, 05:17 PM) That's not true - DAQmx works for M series and E series cards... From http://sine.ni.com/nips/cds/view/p/lang/en/nid/1038' target="_blank">this page: "NI E Series devices come with NI-DAQmx driver software..."

A huge thank you to everyone who attended this evening's LAVA / OpenG NI-Week 2008 BBQ and the Iron Works in Austin, TX! Beef was eaten, Shiner Bock was drunk, and prizes were won, and I'm sure a bunch of photos will be up in the gallery soon (oh, as well as the handful of people that video blogged the proceedings with their National Instruments vblog cameras - don't forget to link to those here!) A big thank you to all the folks who donated the prizes - we had an awesome prize table this year with a Wii, Zunes, professional edition software licenses for both the Endevo GOOP Development System and JKI's VIPM, lava lamps, heaps of t-shirts ("retro" LAVA and VIPM), mousepads, coffee mugs, bumper stickers, a digital desk clock/calendar/thermometer/picture frame, an umbrella... Attendance? I'm glad you asked: we needed to get 100 people there to cover the minimum, and then the Iron Works started charing by the head. As you all know, I was pushing to make sure we had the 100 there (otherwise my PayPal account was going to be a little light ), and to give you context: we got ~70 to our party last year. This year's attendance? 117, making it the biggest LAVA / OpenG NI-Week BBQ ever! We had a rush of "I'm not on the list, so can I please give you cash?" folks, and we filled the Iron Works to the brim. As for the financials, we don't look to make a profit off the BBQ - it's more about having a great time with good folks - our only financial motivation is to try not to loose money. I just did the rough financials, and we came up with a profit of approximately $60, so I'll be sending everyone ~50c in the mail (less the cost of the stamp and envelope). Seriously though - I'll get the left-over $ (once I work it out completely) to Mike to add to the ChipIn fund to help keep out LAVA servers going for a little while longer... Thanks so much y'all - my work here is done ...until next year cheers, Chris

QUOTE (MJE @ Aug 5 2008, 08:04 PM) That's a really good point - there's no real reason to ping the server in this case.

QUOTE (solerpwr07 @ Aug 5 2008, 02:41 PM) Have you checked out Norm's http://forums.lavag.org/Tree-Control-API-file71.html' target="_blank">Tree Control API? It might be just what you're looking for... PS: Please please please change the colour of the BD back to white

QUOTE (Darren @ Aug 5 2008, 02:32 PM) I know you don't need me to say this, but that's a totally valid answer. That said, let's talk about the raodmap (if you can): you said "Look for the Report Gen codebase to become more OOPish in future releases", and, based on your other quote above, what benefit does eventually switching from by-ref to by-val have to the report generation toolkit? It would help me understand the partial switch (wrapping the by-ref in the by-val) more if I understood where you're going with it. Is branching a by-val report really a popular-justified use case? If not, what is/are the use case(s)? If you do make it "more OOPish" (great term by the way - I'll be using that in future ), then that will definately "...make the toolkit behave differently now than it did in past versions". As they say in the acting profession: "what's the motivation?" PS: I appreciate you guys taking time out during NI-Week to keep posting on the fourms. I know how crazy-busy everyone at NI is :thumbup:

QUOTE (Chris Davis @ Aug 4 2008, 03:48 PM) Our internal CVT example isn't quite what you're looking for (you could do what you want with it, but it'd take some work) - I think Ben's nugget is probably your most viable option to start with, but please post back if you get stuck (there are a few other options that I'm not immediately at liberty to disclose :ninja: )

QUOTE (Val Brown @ Aug 3 2008, 05:34 AM) Off topic alert: Why don't you use OpenG? Maybe we should break this into a separate thread...

QUOTE (GaryTan @ Aug 3 2008, 04:18 AM) It's been a long time since I've used NI-IMAQ-USB, but, generally speaking, USB devices are enumerated when you plug them in for the first time. When you say "what will happen", what is it that you want to know?

QUOTE (GraemeJ @ Aug 2 2008, 08:13 PM) I'm sure there'd have to be a scripting node that reads that for each VI, and then you could do some Boolean logic (sorry, a bit flat out at the mo, otherwise I'd try it for you...)

QUOTE (Darren @ Aug 2 2008, 03:22 PM) ...and you're not going to sacrifice his/her name so that we can chatize him/her at NI-Week, are you? QUOTE (Darren @ Aug 2 2008, 03:22 PM) Oh, and as for the object repository, that's a holdover from the original design. The user-facing API became class-based, but some of the underlying code stayed the same. Look for the Report Gen codebase to become more OOPish in future releases. OK - great - that makes me happier.