Can you believe it has already been 2 full years since the first WUELUG? Visiting other companies is starting to become WUELUG’s trademark. This time at WUELUG08, the first meeting of 2020, we visited the premises of iNDTact, right here in Würzburg!
Read more »
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 »
We are always delighted at every new community outreach attempt amongst the LabVIEW users. A new project recently emerged, from Jonathan Hobson, who created the Quick Drop Podcast dedicated to LabVIEW and people involved with its development.
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?
We have been doing a lot of work recently based on the Delacor Queued Message Handler (DQMH). For one of the modules we came up with, the Generic Networking Template for DQMH, I was offered the opportunity to write an article on Delacor’s blog.