Delacor Toolkits Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

issue when create new module from custom template

Solved!
Go to solution
Highlighted

thanks first for this great framework!

 

we made a custom module template, and have created a new module from this template, for the first time.

and curious thing occured, when we tried to create another new module.

here is the error displayed.

royceking_0-1598883707524.png

we finally find the template api tester is moved inside the lvlib automatical, though this api tester is originally included in the "Tester" virtual folder, before the first time we use this template to create a module,like this.

royceking_1-1598884151360.png

 

and if we remove the api tester outside and back to the "Tester" virtual folder again, we can use this template to create new module again without error. but again, the api tester is moved inside the lvlib, and error occured.

 

 

 

 

0 Kudos
Message 1 of 5
(147 Views)
Highlighted

I reported the bug directly to Delacor 2 months ago, and they created an issue.

 

I'm pretty sure that the next version of DQMH will come with a fix 🙂

 

To be curious, I came across the issue because I would like to duplicate an existing module inside my project. I created a feature request for that, by that way --> https://forums.ni.com/t5/DQMH-Feature-Requests/Add-duplicate-module-menu/idi-p/4062011

 

What was your use case?

Olivier JOURDAN

Wovalab | Certified LabVIEW Architect | DQMH Trusted Advisor |
Message 2 of 5
(107 Views)
Highlighted
Solution
Accepted by topic author royceking

@Olivier-JOURDAN wrote:

I reported the bug directly to Delacor 2 months ago, and they created an issue.

 

I'm pretty sure that the next version of DQMH will come with a fix 🙂

 


It will be in the next release.

 

For now, when adding a new DQMH module from template, make sure the module used to create the template is not in the same project as to where you are adding the new module. You could create a blank project just to add your DQMH module and then move the module folder to the correct location. We apologize for the inconvenience and hope the workaround can help you out for now.

 

Thanks again for your trust in DQMH,

Fab

 



Opportunity to learn from experienced developers / entrepeneurs (Steve, Joerg, and Brian amongst them):
DSH Pragmatic Software Development Workshop

DQMH Lead Architect * DQMH Trusted Advisor * Certified LabVIEW Architect * Certified LabVIEW Embedded Developer * Certified Professional Instructor * LabVIEW Champion * Code Janitor

Have you been nice to future you?
Message 3 of 5
(103 Views)
Highlighted

it is similar with your case. we define each test item as a module, and there are almost 40 test items in this project.

 

each test item will be loaded dynamic and we create a module "test execute" to act like a middleware to manage these items.

 

we have refered to HSE application template for way of dynamic loading and registering modules. this framework is a little bit complicated for us, so we just use simple dqmh template.

 

thanks.

0 Kudos
Message 4 of 5
(88 Views)
Highlighted

all right, this is the way out and it works.

looking forward to the next release.

Message 5 of 5
(83 Views)