01-22-2013 12:58 AM
With this modified and new VIs, the VI documentation can be edited in a separate tab page in the Icon Editor. I hope this will motivate writing documentation for your VIs.
Known limitations
Installation
If this does not work do the Installation for Development (see below)
Installation for Development
Links
Initial discussion and discussing development: Suggestion: Edit Documentation form Icon Editor
Original Idea in LabVIEW Idea Exchange: Icon Editor with VI Documentation
01-22-2013 01:23 AM
How this looks:
01-25-2013 01:20 PM
Hey shb,
I am the orignal poster for the idea exchange idea. I am excited someone else is intersted in this. I looked at doing this myself but didn't have any time to work no it currently. I did try downloading you code but it seems like "lv_doc_edit.lvlib" is missing from the zip. I would also like to help you make a compiled version of the icon editor for easier installation.
Let me know when you get that file added to the zip.
Thanks,
Stephen
01-28-2013 10:46 AM
Right...
The lv_doc_edit.lvlib is included now.
As the best method for distributing I see a VIPM package. But I do not known how to build one which replaces NI VIs. (And undoes this changes when being removed.)
Greetings,
shb
03-13-2013 06:23 AM
Changes in V2:
Correct tab page is shown or hidden
Instruction for normal installation is corrected,
packed version for normal installation will follow when I know how to append a 2nd document
changed source files:
added changed file "ShowLayersPalette.vi"
04-03-2016 10:06 PM
Has this (very useful) idea been incorporated into more recent versions of the Icon Editor? I notice that there are Source Distributions for Icon Editor 2013, 2014, and 2015 (and, soon, 2016?) -- have these incorporated the Documentation Edit feature? If not, how difficult would it be to "port forward"? [I fear to examine the code too closely ...]
Bob Schor
04-04-2016 02:18 PM
This feature has not been added to any current versions of LabVIEW as of
2015. I do believe this could be added to any of them but I have not tried
recently as we are using a different documentation tool now.
Stephen