I'm playing with a shared library in Linux Labview. The library needs some development work.
I've come across two annoyances and wonder if anyone has a solution; 1) When rebuilding the library, I have to exit and restart Labview before the new library is picked up- otherwise a cached copy of the one that no longer exists on the disk is used. Maybe I can also close all VIs but that's as inconvenient when developing! 2) I can't seem to specify non-standard library paths in the "Call Library Node"; if I change it to my build directory in order to use the new version instead of the system version, the path appears to change OK but when I go back into the Call Library configuration, the old library path is still there. Oddly, erasing the path does work because the VI becomes broken when I "OK" the change. Both may be related, since 2) may be because the new library is the same name as one already cached when the VI loaded. Is there a way to force LV to reload libraries? -- Dr. Craig Graham, Software Engineer Advanced Analysis and Integration Limited, UK. http://www.aail.co.uk/
