Can anyone tell me if there is a way to perform a peer review of a shared variable library to see what was changed from a previous version, similar to the Compare VIs tool for VIs in the Professional version of the LabVIEW development software?
Thank you for your time and assistance!
Solved! Go to Solution.
If it is being maintained with good "Version documentation" in a Version Control System, you can look at the logs and see what changes were made. I gather you do not have the Compare VIs tool at your disposal, so you'll need to create some form of (possibly a database) "structure" for your note-taking. If you are fortunate that most of the VIs and other code entries are fairly modular, you should be able to open "before" and "after" versions of the code (you might need to independent LabVIEW "instances" to open VIs of the same name) and make notes on what was changed, if necessary.
It may be difficult, however, to beat the "Compare" tool ...
You misunderstand my original comment, and I apologize if I was not clear. I do have access to the Compare VIs tool, and use it extensively to independently verify exactly what was changed between revision A and revision B of a given VI; relying on the check-in comments of the developer is not a rigorous peer review technique.
However, the Compare VIs tool does not work on files of type .lvlib, including those that contain a bunch of shared variables, so it is difficult to tell when, for example, a single shared variable within a list of 20 of them is changed to use a different type definition for its type.
The lvlib file is an XML document. You can use a text compare to see the differences.
When dealing with Project .lvlib files, I use a "file compare" tool (such as a text editor) to compare the (largely text) .lvlib files. When things are really messed up (meaning "Not My Code, thank you very much") (or "only rarely do I make such a mess"), I sometimes do the following:
Note that this omits Libraries (including "Reuse Libraries"), so is not necessarily "Best Practice". But if you are walking up to someone else's
mess disorganized set of files, sometimes "starting over" and working "forward" is easier and quicker than trying to unravel the tangled web.
Thank you Mark, that is exactly what I needed! Simple, easy solution that I was overlooking; I didn't realize that .lvlib are (mostly) plain text files and I can just use my text comparison tool to easily pinpoint exactly what items changed between the two revisions, and frequently the exact ways in which they changed. Perfect!