Automating the build process of your LabVIEW application on a dedicated server as part of a "continuous integration" process for your project is extremely helpful to your team for many reasons. One ...
VIPM has a great "hidden" feature that most people don't know about and are very happily suprised to learn about, when they see me use it.
Over the last several years, touchscreen technology has become a staple feature in our world. At JKI, more and more of our customers are choosing to create their apps using touch UIs in LabVIEW. We...
In my last post on JKI State Machine Best Practices, I explained the #4 Best Practice: Use macros (instead of “chaining” together sequential states).
In my last post on JKI State Machine Best Practices, I explained the #3 Best Practice: Keep the Original Size (i.e. don’t grow the structures). In this post, I'll tell you which best practice came in...
In my last post on JKI State Machine Best Practices, I explained the #2 Best Practice: Don’t add code and logic inside the Event Structure. In this post, I'll tell you which best practice came in...
In my last post on JKI State Machine Best Practices, I explained the #1 Best Practice: Don’t hide your state strings in subVIs. In this post, I'll tell you which best practice came in second place.
At a recent JKI Team “LabVIEW Lunch” (where the team gets together to eat and talk shop), we were discussing JKI State Machine Best Practices. Note: the JKI State Machine, an easy-to-use yet powerful...
