LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

ref.vi in llb can be opened from within during development, not runtime

Hi Clement,

      For what it's worth, like Andre and (i think) Brian, I don't keep VIs in an LLB during development - it takes longer to save VIs after editing when they're stored in LLBs, LLBs aren't suited to source-code-control of individual VIs, and if an LLB gets corrupted (it happens), you can lose lots of work!. Smiley Surprised

I do use LLBs to distribute "Plug-in" Librarys of functions (to be used by an Exe); also, when creating an EXE for distribution, I create an LLB first and build the EXE from the LLB, then archive the LLB with the EXE (so I can Always go back), though, this usage for LLBs can be replaced by source-code-control version labeling and retrieval functions. Smiley Wink

Cheers!

 

"Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)
0 Kudos
Message 11 of 11
(339 Views)