Separate Compiled Code for vi.lib

[code-lux]

To track changes I make in the vi.lib in SCC I set Separate Compiled Code for the affected VIs.

Does Separate Compiled Code for VIs from vi.lib have performance issues for LabVIEW?

Why does NI deliver VIs with included Compiled Code in the vi.lib?

Does anybody have a good proceedure to merge own changes in vi.lib with new LabVIEW patches?

[GerdW]

Hi lux,

---

@code-lux wrote:

Does anybody have a good proceedure to merge own changes in vi.lib with new LabVIEW patches?

---

Generic advice: don't change any code within vi.lib!

Create your own user.lib where you can place copies of code from vi.lib...

[Kyle97330]

---

@code-lux wrote:

Why does NI deliver VIs with included Compiled Code in the vi.lib?

---

Because it's not expected that users should change vi.lib code!

GerdW says "Create your own user.lib where you can place copies of code from vi.lib", which I somewhat agree with except for some nitpicks.

Nitpick 1:

Don't just copy them, copy and rename them.  If you don't rename them, you're almost certain to get conflict popups at some point.

Nitpick 2:

If you honestly feel there's something wrong with vi.lib code, then you might want to post some of what you're doing to it.  Most vi.lib code has been with LabVIEW for decades, and while in some cases it remains unchanged for compatibility, in most cases it remains unchanged because it's working well after having been used by tens of thousands of people.  If you think there's something that "needs" to be fixed (as opposed to adding new features or custom company-specific interactions), there's a reasonable chance you're wrong about it.

[code-lux]

Hi Kyle and Gerd

Thanks for your answers.

Several of the big addons you can get on VIPM are changing the vi.lib and tools like Quickdrop are there and we are officially encouranged to add our own scripting there. And my code is just working fine.

But I find the maintainance of it in case of LabVIEW updates awkward and I hope to get some tips from others how they handle it.

I.e.: did anybody try to Separate Compiled Code for all VIs in vi.lib?

As NI starts to make code open source like Icon Editor and Actor Framwork (both part of vi.lib) I´m optimistic that it will become easier to track changes in the vi.lib