Usually, LabVIEW stores the compiled code used to run a VI together with the graphical code of the VI in the same file. LabVIEW automatically recompiles all changed VIs together with all callers, modifying a lot more files than were actually touched. Your SCC won’t like that! Luckily, there’s an option to separate the compiled code from the graphical source code.Read more »
Using LabVIEW’s VI Scripting features, it is surprisingly easy to create tools that increase development efficiency and enforce coding guidelines. For example, having groups of associated VIs stand out on your block diagrams makes maintenance a lot easier. VI Scripting allows you to add glyphs to VI icons programmatically with very little overhead.Read more »
“Best Practices” are methods or techniques that are accepted as superior to alternative ways, so we should expect anybody to adopt them. Surprisingly, we all dodge best practices – because they’re too complex, too much effort, or too (insert-other-excuse-here). But why not take small steps?