When LabVIEW 2013 discharged, i accustomed be terribly excited regarding LabVIEW Bookmarks. I actually have been victimization them for a year presently, which i feel they are one in each of the foremost productivity-enhancing choices among the entire product labview programming .
What ar bookmarks? Any word preceded by a "#" image at intervals a free label, object label, wire label, or subdiagram label on the diagram. so they're super-easy to form (you merely type!), and in addition really simple to manage with the browse > marker Manager window. And my favorite (often-overlooked) facet of the marker Manager is that it will dissect all of the VIs in your project for bookmarks, even VIs that are not in memory! In my opinion, that's the first profit that the marker Manager provides over the standard notice window .
After victimization bookmarks usually over the past year, I even have discovered three distinct use cases where they're out there in handy:
To-Dos - This one is probably pretty obvious, but whenever there is a neighborhood of code that you simply} just acknowledge you may got to retreat to, stick a #todo marker there and use the marker Manager to return back back to it later.
Benchmarking - once i'm investigation associate outsized app for performance enhancements, i'll sometimes build tweaks in several places to undertake to hurry things up...turning on inlining, setting reentrancy, parallelizing For Loops, etc. I leave bookmarks (#inlined, #reentrant, etc.) where I build these changes to create it simple to return back back to them later if necessary labview programming .
Code Review - I even have a colleague with whom I actually have been doing frequent code reviews, and he's a marker Believer too. it's so nice to form his table for a code review, and to examine the marker Manager already open on his screen, with #review bookmarks ready to bear, outlining all the changes he created.
So if you've got got LabVIEW 2013 or later, you need to terribly begin victimization this nice feature! One final note...if you are victimization the marker Manager to navigate through code that ships with LabVIEW, you'd presumably would like to feature these INI tokens to your LabVIEW INI file:
Without these INI tokens, the marker Manager will not show bookmarks in VIs that board the [LabVIEW 20xx]\vi.lib or [LabVIEW 20xx]\resource folders. clearly i might like these tokens for my add LabVIEW R&D, but i'll admit use cases where different LabVIEW developers might have to be compelled to navigate bookmarks in shipping LabVIEW VIs likewise.
Back once I first introduced quick Drop Keyboard Shortcuts (QDKS) in LabVIEW 2009, I wrote this diary post that mentioned the way to write down your own shortcuts. That information continues to be valid (for LabVIEW 2009, anyway), but it's alittle dated, and doesn't quite discuss all the most points and usefulness on the market of late. Plus, I actually have been asked over and over recently regarding the way to "get started" writing custom QDKS. so this diary post ar aiming to be a a refresher, at the facet of up-to-date information regarding what's presently on the market in LabVIEW 2012 that pertains to QDKS .
There is a plugin model that ships with LabVIEW that you simply} just can use to urge started writing your shortcut:
[LabVIEW 2012]\resource\dialog\QuickDrop\QuickDrop Plugin model.vi
Yes, i do are aware of it need to be a .vit file, and it will be in LabVIEW 2013...but for presently, you've got have to be compelled to avoid wasting your own copy somewhere. Anyway, this VI is full of comment describing but you act adding the desired scripting code for your plugin. The model already includes the support code necessary to line up Associate in Nursing Undo dealings for in spite of operation your plugin performs.