wireworkers,
I have started making some labview libraries (lvlib - new feature in LV8) for generic code reuse.
I noticed that using a library in a project blocks you
from actually editing the library vi's themselves. Great feature!
But then something changed...
Now, when I open any project that uses libraries, I always get full access to the library VI's, even the private ones (albeit through the public VI's). I believe library VI's should be read only when called in another project. Locking the lvlib and making lvlib VI's private does not affect this problem.
Anybody have an idea what happened here?
------------------------------------------------------------------------------------
Seriously concerned about the Labview subscription model
