Modify parts of vi.lib. Specifically NI_MAPro.lvlib

[Corey.Rotunno]

I am working on an application that uses the Waveform with SGL Y_Value representation data type extensively. I have modified vi.lib/Waveform/WDTOps.llb by adding .vi's to the polymorphic .vi's in the library to allow working with the SGL Waveform data type natively. I have documented the changes in our development library repository so anyone else opening the application in development mode can copy my modified WDTOps.llb into their local directory.

I am attempting to do the same with some .llb's in the vi.lib/measure/ directory but I can't because all the .llb's are contained in a locked .lvlib (NI_MAPro.lvlib). Is there anyway to do this neatly? I would really rather add them to the stock polymorphic .vi's than to just copy the block diagram of one of the .vi's, modify it, and then save it in some other directory completely.

In my opinion, I should not have to do any of this - If LabVIEW allows me to specify the Y-Value array in a waveform to be of the SGL datatype, then the stock polymorphic .vi's in the vi.lib directories should include .vi's for working with them natively. I am reading 36 channels at 50kHz....so type casting isn't always a good option if I am doing a function on a streaming basis.

Thanks,

Corey

[altenbach]

I would never touch VI.lib. If you make youw own versions, these belong in user.lib and have distinctive names from the stock version.

[Corey.Rotunno]

Do you have any suggestions on how I might be able to tie the two together. For instance, if I am working with a SGL Waveform and I put down the standard WDT_Index Waveform Array, can I have it point to the .vi in my user.lib? Or I just have to manually communicate to co-workers that if they are working with a SGL waveform rather than a DBL waveform they should be using the VI's contained in user.lib instead of the standard waveform palette.

Thanks for the quick reply btw.