Leaderboard

After years of commercial availability, the VI Helpeks toolkit has transitioned to an open-source project under the terms of the MIT License. Starting with version 3.1, all source code, developer tools, and documentation assets are publicly available on GitHub: https://github.com/konstantin-shifershteyn/vihelpeks Installation and Distribution • VI Package Manager (VIPM): VI Helpeks is listed in the VIPM package repository for direct installation. • Direct Downloads: Distribution packages are available via GitHub and the NI LabVIEW Tools Network. https://github.com/konstantin-shifershteyn/vihelpeks/releases/tag/v3.1.0 https://www.ni.com/en/support/downloads/tools-network/download.vi-helpeks.html#372323 Licensing and Contribution Under the MIT License, users are free to download, install, modify, and integrate the toolkit into both personal and proprietary commercial applications without restriction. Community members are welcome to use the software free of charge and contribute to future development. About VI Helpeks VI Helpeks is a LabVIEW add-on providing UI tools and API VIs for generating professional documentation for VIs and palettes in HTML and CHM formats, matching the native LabVIEW Help style. It has been listed on the LabVIEW Tools Network for many years and was named a finalist for the LabVIEW Tools Network Innovation Product of the Year 2013.

Hi there ! If this subject interest you, I'm currently working on a new State Machine Toolkit for LabVIEW. You can find some shorts videos about it here : https://www.youtube.com/@EmmanuelGeveaux Or some posts about it here : https://www.linkedin.com/posts/emmanuel-geveaux-93836130a_labview-statemachines-ugcPost-746286803261... This toolkit will be Open-Source, free for students, education purpose and within LabVIEW Community Edition use. I'd be happy to ear any feedback on those videos and posts. Best regards Emmanuel

I have been working on an architecture that uses VI Server to send messages between application instances, both local and across the network. One of the problems I have run into is the fact that VI Server calls are blocked by activity in the root loop (sometimes referred to as the UI Thread). There are several things that can cause this: other VI server calls, system dialogs (calls to the one and two button dialog functions), if the user drops down a menu but does not make a selection... (I'm sure there are more...) Since this is a pretty normal way of communicating between applications, I was wondering if anyone had any ideas for a work around. Here is a basic description of my architecture: Message is created and sent to local VI that sends to outside application instance. Local sending VI opens VI server connection to remote instance. It then calls a VI in the remote instance that takes the message as input. This remote VI them places the message in the appropriate queue on the remote instance so it gets handled. If the remote instance root loop is blocked, the sending VI on the local machine is also blocked. I could try to eliminate all system dialogs from the remote application, but that only partially addresses the issue. I really wish a future version of LabVIEW would eliminate this problem with the root loop and VI Server all together. BTW: using LV2012 but this issue exists in all versions. -John

That custom control editor is one of the more arcane parts of LabVIEW. It exists since at least LabVIEW 2 and has seen only small improvements since. And according to its original creator back at that time it is a pretty nasty piece of software code that would need a complete rewrite to be able to make more elaborate modifications to it. Chances for that to happen are about 0.0something % nowadays. Unless someone somewhere is willing to pour a few millions into this. 😎