Leaderboard

Please see the above link to download the videos The NIWeek 2014 Videos are compressed and ready for down load from Tecnova's ftp server I would strongly recommend using an ftp client to transfer them to your computer. A web browser may work but if you want to download multiple videos the ftp client makes things much easier. My ftp client of choice is FileZilla and it is free. FileZilla can be downloaded at http://filezilla-project.org/ ftp://frc.tecnova.com login: LabVIEW_Videos pw: LabVIEW login and password is case sensitive. if you are using Filezilla your site manager window will look like this. A big thank you to Dan Bosdech for recording the sessions on Thursday as I was attending a private all day session. Enjoy and let me know if there are any issues. Mark

The hallmark of an experienced LabVIEW developer is the usage of their or others templates which prevent the ubiquitous blank block diagram symptom where time is wasted doing the same thing that they have done before. Attached and linked you will find the TLB` (prime) template which, after a little learning what the parts are, can take you from zero to 60 in no time the next time you need to create a Top-Level application or interface. This template can be used from the ultra simple UI to a fairly complex application. Many questions and comments have been made about the original design (TLB) which is located here http://lavag.org/topic/14164-discuss-tlb-top-level-baseline/ This reason for the update in this design is detailed in the presentation "Rebirth of the LabVIEW State Machine" which is accessible here http://lavag.org/topic/16091-ni-week-2012-videos/page__view__findpost__p__97844 Installing and Creating http://screencast.com/t/vtlFgLhQqT Review of Examples http://screencast.com/t/XLIN0yjS Structure of Code http://screencast.com/t/5RtMhPVujS Basic Flow of Operational Code http://screencast.com/t/1QGFRRuSf0nT Adding a control to the system http://screencast.com/t/IJTxEQ28 Adding an action to the system http://screencast.com/t/5984lGlMjM <More to come soon> QSM Evolution.zip Code used in presentation video detailing why the typical QMH is fraught with issues that we have all run into Credit to Daklu for it's creation and sharing ni_tool_tlb`-1.2.0.23.vip Most up to date version of TLB` Rebirth of the LabVIEW State Machine.pptx TLB` Application Template.vipc

I almost didn't get them finished in time, but I will be donating a hand-made necklace and bracelet featuring the "top" (ahem) new feature of LabVIEW 2014! That's right, the launch icon! They're reversible: 32-bit launch icon on one side, and 64-bit on the other. Some assembly required: I'm not tying off the cords so you can adjust them to fit. [i've been told men might not want to wear a necklace, but, hey, you could always share with someone special!] Brought to you by Christina Rogers, member of LabVIEW R&D, author of the Eyes on VIs blog, and creator of the (free!) graphical novel Rune: A Tale of Wizards and Kings and sequel novella Wizards and Kings: Sacrifice (only 99 cents on Kindle, and free with Kindle Unlimited!)

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..