Additional customization when creating a new DQMH Module

[joerg.hampel]

I propose there be more items you can configure for a DQMH Module when creating it from scratch (ie not from a template). My current ideas are:

1. Name of the virtual folder in the target project to place the module tester

2. Name of the virtual folder in the target project to place the module library

3. Alternate path (other than "Libraries") to store the new module library on disk relative to the target project.

For example, our way of working defines that our DQMH modules are stored in a separate folder for each module under a /Modules folder. So a PowerSupply module would be stored in /Modules/PowerSupply/, both on disk and in the project as virtual folder. 

My suggestion is to have:

1. A way to enter these pieces of information directly when creating a new module

2. A way to store the defaults for these values "somewhere" (either in the LabVIEW.ini or maybe some other, user-specific place)

[Jens_S]

I'm doing exactly the same for my DQHM projects so 100% agree, would be very nice to have these features.

Maybe save the default values as an part of a LV project inside a DQMH.ini or something like this.

[Olivier-JOURDAN]

Should be in DQMH 6.1.

Thank you for the suggestion 🙂