crelf

QUOTE (ShaunR @ Apr 16 2009, 06:05 PM) No worries - who should I send my rate schedule to?

QUOTE (twinsemi @ Apr 16 2009, 11:32 AM) You totally need to use the http://wiki.lavag.org/Insane_Objects' rel='nofollow' target="_blank">peak heap function. Everytime I've gotten an insane object, peak heap has been my saviour :worship:

QUOTE (hooovahh @ Apr 16 2009, 09:37 AM) I sooooooo don't agree. Check out the http://zone.ni.com/devzone/cda/tut/p/id/7198' target="_blank">large apps site at ni.com.

QUOTE (asbo @ Apr 15 2009, 11:11 PM)

QUOTE (normandinf @ Apr 14 2009, 06:38 PM) Code I did 10 years ago makes my eyes bleed ~

QUOTE (Cat @ Apr 14 2009, 10:17 AM) Is it really cluttering up the folder? I mean, it's not often that users should be playing around in there, so I don't think it's existance is too compelling a reason to circumvent it. That said, if there are settings in there that you definately don't want your user screwing with, then that's a different story...

You should totally get a professional to write the driver for you to at least the level of an NI certified driver for you.

QUOTE (jzoller @ Apr 14 2009, 01:15 PM) Whilst I enjoy poking fun at others' code as much as the next bloke, I'm not sure that all of those metrics are particularily valuable. I know that my code would look pretty bad on a few of those metrics, and I consider myself a very particular programmer. Either way, I don't think we should be relying on NI to define what good programming style is, nor should we necessarily be expecting them to adhere to what we think is good programming style. I could be wrong, but I don't think many people look to Miscrosoft as the ultimate when it comes to VB style - most people look to books written by professionals that *use* VB, not those who write VB.

QUOTE (ShaunR @ Apr 13 2009, 03:32 PM) Make sure there is a requirement to go wireless - some sites specifically rule-out wirelss (military, standards comissions, etc).

QUOTE (JustinReina @ Apr 13 2009, 02:39 PM) Yeah, but NI has the http://forums.lavag.org/blog/crelfs_technology_articles/index.php?showentry=188' target="_blank">patent on rectangles.

I think the correct answer is D, but I'll bet a beer that NI's after C. :!: Remember folks: if you don't like the exam questions, pontificating here is fun, but if you actually want something done about it, contact NI (and post 'em a link back to this thread).

QUOTE (Aristos Queue @ Apr 12 2009, 04:34 PM) Ha! Just another example where the engineering and sporting worlds a complete opposites

QUOTE (PaulG. @ Apr 10 2009, 03:43 PM) Then your boss needs to learn the difference between cost and value For every system I've made that does anything even mildy interesting wrt sequencing, the time I've saved by using TestStand rather than trying to do it myself has far out weighed the purchase and distribution prices. Use the right tool for the job - I don't know who said it, but I agree that you should be concentrating on the design of tests and the low level stuff - having to design, write, test, deploy and maintain your own custom sequencer isn't a good move in the medium to long term.

QUOTE (jcarmody @ Apr 10 2009, 03:09 PM) I htink you're confusing TestStand with Labwindows/CVI?

QUOTE (jdunham @ Apr 10 2009, 11:27 AM) :thumbup: Very well put.

QUOTE (asbo @ Apr 10 2009, 07:58 AM) http://lavag.org/old_files/monthly_04_2009/post-181-1239377374.png' target="_blank">

QUOTE (Justin Goeres @ Apr 10 2009, 09:03 AM) You totally had me until the comma. I completely agree with the unit testing, but I think the second part of that sentence is irrelevant, and possibly incite-ful. If you successfully unit test your code to well written requirements (usling standard processes, of course) then you're covered - the system design need not be considered.

QUOTE (Darren @ Apr 9 2009, 11:20 AM) Another "stupid-foriegner" story: I had no idea what a "pound key" was when I came to the US. I'd call into conference lines that said "enter your conference code followed by the pound key". I'd look at the phone and think "where's the £? Maybe just this particular phone I'm using doesn't have one. I'll just mash the keypad until I get the operator." In other countries, we call it the hash key (not to be confused as a speed dial to order illicit drugs. QUOTE (Justin Goeres @ Apr 9 2009, 12:25 PM) ...That's why unit testing is so critical, because it verifies all the behaviors of the software that matter. That's a great way of putting it Justin. IMHO, you can put whatever the hell you like in the code you deliver to me, as long as it is proven to meet my requirements. The way to do that is to make sure there are appropriate and tracable requirements, and you use accepted testing to proove you met said requirements.

QUOTE (hooovahh @ Apr 9 2009, 09:31 AM) If a product needs to know the real time, you can write a call to a http://en.wikipedia.org/wiki/Time_server' rel='nofollow' target="_blank">network time server through NTP (if your system has access to the internet).

QUOTE (PaulG. @ Apr 8 2009, 09:47 PM) Make sure you get down there in early August so you can get some LabVIEW goodness while you're there! :thumbup:

QUOTE (Justin Goeres @ Apr 8 2009, 02:25 PM) That goes without saying Justin, but thanks for saying it anyway

QUOTE (Neville D @ Apr 8 2009, 01:27 PM) Oh, yes, you're right - sorry - I was thinking of something else. QUOTE (Matthew Zaleski @ Apr 8 2009, 01:46 PM) Thanks Chris. I've bookmarked that NI page for further review. Anytime. I discovered it recently when an end-user's PC just needed some DAQ goodness on it, and I didn't want them to have access to anything through MAX. Sure enough, using this method it doesn't even install MAX :thumbup:

QUOTE (ggatling @ Apr 8 2009, 11:07 AM) Ha! Well put. You might not be confusing them, but I think others are... QUOTE (ggatling @ Apr 8 2009, 11:07 AM) There is a balance somewhere between adding inovative new features and refactoring, debugging, or otherwise fixing existing code. I'm not sure where the Right Place is on that spectrum, if there is one, but I was making the argument that I feel like NI does not incorperate enough of the latter, especially given the fact that to get the bug fixes I must also accept the new features. Gotcha. I think that, irrespective of instability moans, that NI will continue to innovate. Just as long as they do so while, in parallel, they fix issues. I think they do a pretty good job of it (especially when you look at the publically exposed issues-fixed lists that come with each new version - imagine how many are on the private one ), considering the size of their team and the size of (read: incoming cash flow from) their client base. I'm not saying that the process is perfect, but for what we've got, it's not horrible.

QUOTE (Matthew Zaleski @ Apr 8 2009, 10:53 AM) I'm not in front of my system at the moment, so this might be a little rusty: when you're in the build installer dialog, and you select DAQ as one of the things to install, there is an option in the top right where you can select between 5 types. From http://zone.ni.com/devzone/cda/tut/p/id/5434' target="_blank">NI's website: QUOTE Q: Can I make NI-DAQmx smaller so that it doesn't take up so much disk space? A: You can select different runtimes of the NI-DAQmx driver to decrease the disk space by more than 70 percent. This allows you to repackage NI-DAQmx so that you can install it with your deployed applications. NI-DAQmx installs much more than just the basic .dll driver. NI-DAQmx is a componentized, extensible driver software package featuring necessary components required to simplify configuration, device management, development, and cross-device functionality. In addition, NI-DAQmx includes a set of measurement services which go far beyond a basic API to make device function calls. NI-DAQmx includes LabVIEW SignalExpress LE, Measurement and Automation Explorer (MAX), documentation, examples, and the DAQ Assistant. The NI-DAQmx installer extracts the installation files to your hard disk in the C:\National Instruments Downloads\NI-DAQmx folder. After the installation of NI-DAQmx is complete, the installation files remain on the hard disk and take up close to 1 GB of disk space. If you ever need to free up disk space on your hard disk, you can delete these files without affecting the functionality of NI-DAQmx. However, in the future, if you wish to install additional features of NI-DAQmx or include NI-DAQmx in an installer created in LabVIEW, you must extract these files back onto your hard disk or place them on a CD-ROM. There's a table on ni.com somewhere, but I can't find it right now.

I'm going to say this one more time: you are confusing undocumented features with experimental features. They are not the same. If the software *you* create with LabVIEW uses undocumented LabVIEW features (like scripting, since that seems to be everyone's hot-button at the moment), then that is *your* responsibility. If you're using undocumented features (and, truth be told, we usually do because we've gone digging for them), then you're introducing a risk. It's not NI's fault that you chose to use them - it's *yours*. That said, I use undocumented features in my architectural designs all the time - I know that they're risky, but I also use them for their feature pay-off. It's my risk, and I'm willing to take it. As an aside - scripting is *not* experimental, it's just undocumented... for now. QUOTE (shoneill @ Apr 8 2009, 04:41 AM) I think it would be more valuable to ask how many people would be willing to foot the bill for a LTS version of LabVIEW. I don't know, of course, but I'd say the response would be very low. NI is a company that needs to make money, and unless y'all can band together and put your money where your mouth is, then it's not going to happen. As a parallel, I think the number of customers that are willing to pay for LTS are even smaller than those who want support for everything NI on the Mac, and that's not going to happen either.