DQMH Consortium Toolkits Feature Requests

cancel
Showing results for 
Search instead for 
Did you mean: 
CyGa

Connect the controls on the scripting GUIs to the connector pane or give an API to feed / act on controls

Status: Declined

DQMH philosophy relies on having module API testers always executable. We are not keen on encouraging event creation automation that would break this concept.

 

@CyGa please contact the DQMH consortium if you steel need this feature

Hi,

 

Including DQMH modules into our application framework, we need to script the creation of new modules / requests and so on.

 

However, current scripting GUIs do not have any controls connected to the connector pane.

Also, even if we could pass some values to these interfaces, we would even need to control if we want to show their HMI or control the creation / cancellation of a scripting action whitout having to press on the OK / Cancel button.

 

Allowing to programmatically control the DQMH scripting VIs would be great !!

CLA, CTA, LV Champion
View Cyril Gambini's profile on LinkedIn
This post is made under CC BY 4.0 DEED licensing
1 Comment
Olivier-JOURDAN
Active Participant
Status changed to: Declined

DQMH philosophy relies on having module API testers always executable. We are not keen on encouraging event creation automation that would break this concept.

 

@CyGa please contact the DQMH consortium if you steel need this feature


Olivier Jourdan

Wovalab founder | DQMH Consortium board member | LinkedIn |

Stop writing your LabVIEW code documentation, use Antidoc!