My use case is simple :
I have a module that uses DAQmx functions, so the module's main VI will only be executable in DAQmx is installed.
Having a public VI from the module to check if the main.vi is executable is, I think, the fastest way for my app to report that a feature is not available due to missing driver.
We have two ears and one mouth so that we can listen twice as much as we speak.
Epictetus
Antoine Chalons
After consideration and discussion, we decided to decline this feature request.
The Consortium and the DQMH members agree that this is something that can be achieved with module templates for individual use cases.
We really appreciate your input, declining the idea does not mean it didn't help us fine-tune the scope of DQMH and reconsider our strategy. Please keep those ideas coming 😉