02-20-2015 10:26 AM
I probably missing something but here is a question:
Suppose i developed Labview library A.lvlib.
Then i developed library B.lvlib which uses public VIs from A.lvlib.
Then i developed new version of A say A1.lvlib which has the same public VIs with the same connectors but different implementation internally.
How do I tell library B to use A1 instead of A short from editing every single vi in B?
Thanks
02-20-2015 12:13 PM
Sounds like a good place for Object Oriented Programming. You could just let the dynamic dispact take care of it all for you. But that is beside the point.
The only decent way I have found to do this is to delete the old library (A.lvlib and all of its associated files) and then try to open the VIs you want to use A1.lvlib with. Then you just use the search dialogs when it can't find the VI from A.lvlib.
02-20-2015 12:29 PM
Thanks, i'll try this
02-20-2015 01:19 PM - edited 02-20-2015 01:19 PM
Another method I've had success with is to open the new A library first, then open the B library. If the library names are the same and the VIs are named the same, then the B will start loading its dependencies and see that A.lvlib::function.vi already exists in memory and it will use it instead of the original one. After loading B it will have a dialog showing that dependencies were loaded from an unexpected location. Then a Save All will cause all B functions to find the new A.
This makes me nervous so I usually do as crossrulz suggested and delete the original A, or just move its location to where the search can't find it, to ensure it finds the new A.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord