DQMH Consortium Toolkits Feature Requests

cancel
Showing results for 
Search instead for 
Did you mean: 
0 Kudos
amaury74

Add the possibility to select more than one module when creating a new event

Status: Declined

amaury74, after reviewing your idea and discussing it internally, we decided to decline it.

 

For modules of a similar type (ie when thinking about default events), a module template might do the trick for you.

 

A future version of DQMH will provide post-scripting hooks, and perhaps even a scripting API, which would allow DQMH users to implement this and similar features themselves.

 

Again, thank you for your input; it is most appreciated. Please keep those ideas coming!

When creating a batch of modules at the begining of a new project, it may be usefull to be able to create a new event in more than one module at a time.

 

amaury74_0-1722495029401.png

 

 

4 Comments
amaury74
Member

PS : one use case is to create a common methode to all module, like ReadConfig or things like that.

ChrisFarmerWIS
Active Participant

A workaround for this idea is to create a template, or set of templates that includes additional default items in your module, such as "Read Config" request.  So that when you are creating a new project, instead of using the out of the box DQMH singleton or cloneable modules, you use your own templates.

Christopher Farmer

Certified LabVIEW Architect and LabVIEW Champion
DQMH Trusted Advisor
https://wiredinsoftware.com.au

joerg.hampel
Active Participant

I second Chris, templates should be quite helpful for your use case.

 

As an alternative, we created our own scripting tools that will augment vanilla DQMH modules with specific additional features.




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 )


joerg.hampel
Active Participant
Status changed to: Declined

amaury74, after reviewing your idea and discussing it internally, we decided to decline it.

 

For modules of a similar type (ie when thinking about default events), a module template might do the trick for you.

 

A future version of DQMH will provide post-scripting hooks, and perhaps even a scripting API, which would allow DQMH users to implement this and similar features themselves.

 

Again, thank you for your input; it is most appreciated. Please keep those ideas coming!




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 )