When LabVIEW 2013 free, i wont to be terribly excited relating to labview programming. I even have been exploitation them for a year presently, which i feel they are one in every of the foremost productivity-enhancing choices at intervals the entire product.
What unit of measurement bookmarks? Any word preceded by a "#" image among a free label, object label, wire label, or subdiagram label on the diagram. thus they're super-easy to form (you merely type!), and in addition very simple to manage with the scan > marker Manager window. And my favorite (often-overlooked) aspect of the marker Manager is that it will analyse all of the VIs in your project for bookmarks,even VIs that do not appear to be in memory! In my opinion, that's the first profit that the marker Manager provides over the standard understand window.
After exploitation bookmarks usually over the past year, I even have discovered three distinct use cases where they're offered in handy:
To-Dos - This one is maybe pretty obvious, but whenever there is a neighborhood of code that you simply} just acknowledge you'll need to come back, stick a #todo marker there and use the marker Manager to come back back back thereto later Visit now.
Benchmarking - once i'm work associate degree outsized app for performance enhancements, i will be able to typically build tweaks in several places to try to to 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 make it simple to come back back back to them later if necessary.
Code Review - I even have a colleague with whom I even have been doing frequent code reviews, and he's a marker Believer too. it's thus nice to hit his table for a code review, and to look at the marker Manager already open on his screen, with #review bookmarks ready to bear, outlining all the changes he created Click here .
So if you have LabVIEW 2013 or later, you want to terribly begin exploitation this nice feature! One final note...if you are exploitation the marker Manager to navigate through code that ships with LabVIEW, you'd probably want to feature these INI tokens to your LabVIEW INI file: