Leaderboard

Guys, guys, I for one am delighted at the increasingly barren "new features" list for each LV release. I've been using LV for many years and have grown to love hate accept many of its idiosyncracies as being de-facto standards. Bugfixes are cool, new features = new bugs. I don't like bugs and as much as I'd love Interfaces for LVOOP and a host of other things, at the moment, bugs and stability issues are my main source of pain with LabVIEW at the moment. Daily crashes, huge delays when editing VIs in projects used on multiple targets simultaneously.... LV needs major repair work. We would all most likely agree on that. The 20+ year old code base is no longer an adolescent and really needs to get its act together. There are certain kinds of petulant and stubborn behaviour which may be acceptable for a teenager, but at the tender age of 28, its time we raised our expectations. Minor rumblings from NI (and quite possibly some optimistic pattern recognition on my part) have led me to have some hope that this process of repair or self-improvement is already underway. I for one look forward to the day where all of the fixing in the background can finally be accelerated because a lot of the old crap (there's no other word for it) has been cleaned out and the source code for LV is finally in better shape. As someone who has been crying for better stability for years, I am delighted to see shorter and shorter "new feature" lists because I'm optimistic and believe the time spent NOT implementing new features has been used for a much more valuable long-term goal. So my message is, have faith. PS Yeah, I wrote behaviour with a "u". I won't give in to the LAVA spell-checker. I won't..

Is there any SSH love added to 2014? The Internet Toolkit went unsupported last year and it's been 4 years of waiting for native SSH. Something I can actually use would be far better than a new icon or bundling the Report Generation Toolkit ( that my boss just purchased two weeks ago and is now part of Pro; thanks sales rep; we'll have to remember that when SSP renewal comes around ).

As someone who has applications that demand 64-bit architecture, I'm glad to see it adopted beyond Windows even if I'm platform locked for the time being. I can only hope support for these platforms becomes more mainstream. Also, this: That was one of the worst and longest lived bugs in LabVIEW that caused me no end to grief. I won't be able to upgrade for a bit, but this single issue alone makes me think it will be a great patch release as far as code maintenance goes.

Okay just finished installing and a few things stick out. The Full and Professional include PID and Fuzzy Logic, and the Professional now includes, Database Connectivity, Desktop Execution, Report Generation, Unit Test, and the VI Analyzer. Doesn't this make the Developer Suite appear less attractive because compared to last year there are less things between a Professional and a Developer Suite? Does this mean NI will be lowering the price of the Developer Suite? It also has a section talking about Automated Test Suite, Embedded Control and Monitoring Suite, and the HIL and Real-Time Test Suite but the link is broken at the moment. It is listed at the moment as http://www.ni.com/labview/suites The Clear Errors which allows to specify an error code only accepts a scalar and not an array of errors to clear. The OpenG versions have existed since version 6.x or so and supports scalar or array as a polymorphic VI. I'm curious to see how the TDMS Set Properties NI_MinimumBufferSize affects performance, and file size when used right. One could argue that the High Resolution Relative Seconds is an idea exchange item and should be mentioned. Also the Hidden Gems mentioned in that idea exchange puts it on the palette among other goodies for other versions of LabVIEW. The Replace with Case Selector feature is nice. You select an input tunnel and it basically wires the case selector tunnel through it. That means this works for any datatype including error, string, enum, etc. Is Path and Not Empty is nice. I've made my own over the years but still nice to see it native. Custom documentation is nice for things like linking to PDFs. Same goes for linking to PDFs in the help menu. I've been able to do this just by having a VI in the help menu that opens the PDF. Application Builder now can make a folder with the version of the build which is super nice. But I've been doing this with Post-Build VIs.