Has anyone considered how to minimize documentation effort thru various LabWindows/CVI programming style guides plus whatever built-in features are available? There's the HTML generator with the ///HIFUN and so on, but there must be more to do Doxygen-like documentation without excessive effort. I'm working thru code I had a student intern develop, and of course I provided no guidance for programming style so am having trouble. I'd like to work thru the code to revise it for readability and correct some functional problems. Biggest problem is I'll work LabWindows for a bit, then drop it for months to work some other aspect of a project (embedded system design including circuit board design, analog circuits, microcontroller code, and of course user interface with LabWindows). When I come back, I need to leave some notes to reduce my time to get up-to-speed again.
Thanks!