@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.
