DQMH Consortium Toolkits Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

GUI for a DQMH module?

Solved!
Go to solution
0 Kudos
Message 11 of 14
(1,398 Views)

"optionally, add a button and event case to the main.vi for a new request, to be able to trigger the same MHL case from the module's UI."


I have checked one of the main.vi-s you linked in a different topic and now I guess I understand this comment a lot better than before. So are you suggesting that the main.vi can be used as something displayed to the user? I never thought about this, but for the first sight it makes sense.

0 Kudos
Message 12 of 14
(1,370 Views)
Solution
Accepted by topic author 1984

@1984 wrote:
So are you suggesting that the main.vi can be used as something displayed to the user? 

Yes, definitely! For our applications, anything the user gets to see is a main.vi of some DQMH module. Could be a pure UI module, could be a functional module with added UI.

 

For low-level modules, it's quite handy to use the main.vi's front panel for a "manual mode" or "expert view" (different customers have different names for this)...




DSH Pragmatic Software Development Workshops (Fab, Steve, Brian and me)
Release Automation Tools for LabVIEW (CI/CD integration with LabVIEW)
HSE Discord Server (Discuss our free and commercial tools and services)
DQMH® (Developer Experience that makes you smile )


Message 13 of 14
(1,365 Views)

Awesome! I guess this subject is something I really did overthink while a relatively simple solution was just right before my eyes. Thanks!

Message 14 of 14
(1,358 Views)