When LabVIEW 2013 free, i used to be very excited regarding labview programming . i have been exploitation them for a year currently, and that i feel they're one amongst the foremost productivity-enhancing options within the whole product.
What area unit bookmarks? Any word preceded by a "#" image among a free label, object label, wire label, or subdiagram label on the diagram. therefore they are super-easy to make (you simply type!), and additionally terribly straightforward to manage with the read > marker Manager window. And my favorite (often-overlooked) facet of the marker Manager is that it'll analyse all of the VIs in your project for bookmarks,even VIs that don't seem to be in memory! In my opinion, that is the primary profit that the marker Manager provides over the quality realize window.
After exploitation bookmarks often over the past year, I actually have discovered 3 distinct use cases wherever they are available in handy:
To-Dos - This one is perhaps pretty obvious, however whenever there's a neighborhood of code that you just recognize you'll have to return, stick a #todo marker there and use the marker Manager to come back back to that later Visit now.
Benchmarking - once i am work an oversized app for performance enhancements, i will usually build tweaks in many places to do to hurry things up...turning on inlining, setting reentrancy, parallelizing For Loops, etc. I leave bookmarks (#inlined, #reentrant, etc.) wherever I build these changes to create it straightforward to come back back to them later if necessary.
Code Review - I actually have a colleague with whom i have been doing frequent code reviews, and he is a marker Believer too. it's therefore nice to hit his table for a code review, and to examine the marker Manager already open on his screen, with #review bookmarks able to undergo, outlining all the changes he created Click here.
So if you've got LabVIEW 2013 or later, you must very begin exploitation this nice feature! One final note...if you're exploitation the marker Manager to navigate through code that ships with LabVIEW, you would possibly wish to feature these INI tokens to your LabVIEW INI file: