DQMH Consortium Toolkits Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

DQMH 5.0 Error message takes the Module Name as an input but it is already in the VI

As K_Bull noted in the feature request document here:

https://forums.ni.com/t5/Delacor-Toolkits-Documents/DQMH-Feature-Requests/tac-p/4047287/highlight/tr...

 

Yes, the DQMH 5.0 Validation tool adds the DQMH Module name which is redundant because the VI already has the Module Name inside of the code.

 

We added this as a placeholder for a much better feature that will come later: including in the error reporting where the error originated. We didn't get to that feature in time for DQMH 5.0 release. We discussed removing the validate/fixer but opted for leaving it there. When the new feature comes, we will use the module name as a guideline to where to make the replacement via scripting.

 

For an opportunity to learn from experienced developers / entrepeneurs (Steve, Joerg, and Brian amongst them):
Check out 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 1 of 2
(787 Views)

Thanks Fab, looking forward to what's in store 🙂

Message 2 of 2
(729 Views)