Announcing DQMH 5.0 Beta

[FabiolaDelaCueva]

Hello,

We have released publicly the DQMH 5.0 Beta version. 

This is a major release and we have taken care of testing it thoroughly. We have been using it in internal projects as well as with customer projects. The only reason we have not released it via the Tools Network is that we still need to complete updating the Help, the documentation, and some videos explaining all the new features. The best way to find out all the new features is by validating an existing module, it will guide you through all the changes. By the way, we made it so now you can validate your modules as soon as you complete upgrading the DQMH toolkit. Please note that you should wait until VIPM  completely finishes installing everything before running the Validation.

Let us know if you have any questions, comments, or feedback.

For complaints: The FREE DQMH toolkit has an extremely generous guarantee: If at any time you are not 100% satisfied with it, contact us and we will gladly issue a full refund of the price you paid 🙂

The main features listed in the Release Notes are:

1. Singleton and Cloneable Module templates updated to use Start Async Call instead of Run VI method for launching Main VI
2. Added support for scripting an RT tester for Singleton modules (DQMH 4.2 only supported LabVIEW Real-Time for Cloneable modules)
3. DQMH Validate Tool improvements:
   1. Prompt the user to run the validate module tool after upgrading DQMH via VIPM
   2. Added the ability to validate all modules in the project. We also added a VI (Validate DQMH Module (Headless).vi) that you can pass in a project path and it will programmatically validate all modules in the project and return a result. This VI could be used as part of a CI/CD process to validate DQMH modules
   3. Added a button to the Validation Results UI that allows you to analyze another module after you are done viewing the results for the current module. We also added a button to the ‘all tests passed’ dialog to allow you to validate another module as well
4. Improved API Tester developer experience: The API Tester does not stop the module on exit if it was already running when the API Tester started running. This is useful when using the API Tester as a sniffer
5. Request and Wait for Reply now return an error if the reply times-out
6. If your custom DQMH template requires a different enqueue (for example for a DQMH Queue child or if the DQMH libraries were built into a PPL), we added the ability to specify a custom enqueue message VI to be scripted into the MHL when creating request events Singleton and Cloneable Module templates updated to use Start Async Call instead of Run VI method for launching Main VI

[Tepig]

Hi, Does Delacor have a plan to develop and release DQMH for LabVIEW NXG?

[TiTou]

I don't mean to preempt on Delacor, but I suggest you read this discusssion from not so long ago : DQMH and NXG

A great part of makes DQMH what it is is the scripting tools, currently NXG doesn't have these scripting tools natively (I heard they can be implemented in C#).

So I guess the question is actually for NI, if / when they are going to implement scripting natively in NXG. The alternative would be to find someone willing to write it in C#.

So if you like DQMH and want it for NXG, contact your NI representative and tell them you will start considering NXG when it has scripting.

[Konan__]

What do you mean "refund"?

Isn't DQMH always been free?

Will 5.0 be under paid license?

[joerg.hampel]

---

@Konan__ wrote:

What do you mean "refund"?

Isn't DQMH always been free?

Will 5.0 be under paid license?

---

Don't worry, Fab just said this in jest!

Seeing as DQMH is a free toolkit, you don't have to pay for it. I.e. you get all that awesomeness for free! So, by saying that Delacor will gladly refund you, Fab just emphasizes the fact that you don't have to pay anything for it in the first place, in a funny way.

Thank you, Delacor, for the very considerate license fee (i.e. EUR 0,-) and your generous refund policy 😉

[FabiolaDelaCueva]

---

@Konan__ wrote:

What do you mean "refund"?

Isn't DQMH always been free?

Will 5.0 be under paid license?

---

As Joerg mentioned, it was my poor attempt at being funny,  I even added the word free in the sentence. 

DQMH is free,  you can continue to download if for free. 

That said, if anybody would like to pay for DQMH, I won't stop them,  contact us and we can give you a special license that you pay for 🙂 (We have done it in the past for some companies that their legal department wanted specific license terms).

The package that you download via VIPM is free and will continue to be free

Happy wiring,

Fab

[Jens_S]

Hello!

First of all, thanks for this awesome tool and the work you put into this 👍

Right now, I'm updating a rather small Project (just 13 modules) to version 5.0 and there is one little thing that could be improved in my opinion. After updating to version 5 I started the validation tool to update my existing modules. After scanning the modules, you get a list of issues to fix where you have to click every single issue and fix it by clicking the “Fix Issues” button. It would be very convenient to have a “Fix All Issues” button.

Best regards

Jens

[FabiolaDelaCueva]

---

@Jens_S wrote:

Hello!

First of all, thanks for this awesome tool and the work you put into this 👍

Right now, I'm updating a rather small Project (just 13 modules) to version 5.0 and there is one little thing that could be improved in my opinion. After updating to version 5 I started the validation tool to update my existing modules. After scanning the modules, you get a list of issues to fix where you have to click every single issue and fix it by clicking the “Fix Issues” button. It would be very convenient to have a “Fix All Issues” button.

Best regards

Jens

---

Hi Jens,

While that would be convenient it would also be dangerous. We want to make sure that you are aware of all the changes that we are doing to your code. You could even do a commit after every fix so you can go back to see what your code looked like before each fix. 

There is also an explanation on the right of what each fix would do.

I have created case DQMHWL-56 for us to look into this in more detail. If you want, you can add this as a feature request at

https://forums.ni.com/t5/Delacor-Toolkits-Documents/DQMH-Feature-Requests/ta-p/3537845

and link back to this discussion (https://forums.ni.com/t5/Delacor-Toolkits-Discussions/Announcing-DQMH-5-0-Beta/m-p/4031704/highlight...)

Thanks for your trust in DQMH and in our team.

Fab

[henriksandin]

Hey Fab and Delacor!

Thanks again for an awesome product that I use in many of my applications. I sent an email a while ago to Delacor asking about where I can find a "user agreement" license text that I would like to add in my "About" window for some code that I will be sending out outside my own team. Where can I find that text?

2nd question: When I update to 5.0 do I HAVE TO update any and all projects that were using 4.2 to be able to make changes to them now or can I decide to keep some Modules running with 4.2 while others (and any new modules) are running 5.0?

Cheers

Henrik 

[joerg.hampel]

The license agreement for DQMH can be found in VI Package Manager:

Regarding 2, the DQMH scripting tools are installed centrally, i.e. you can only have one single version installed at any time. 

Upgrading the toolkit itself will not modify any of your existing modules, but if you make any modifications to pre-5.0 modules, these modifications will adhere to the 5.0 feature set. 

Also, in case you're not aware, the DQMH Validator is a tool that comes with DQMH, which will analyze a DQMH module and suggest fixes to implement the improvements from the newer versions. This works in almost all cases (unless your modifications prevent the scripting from implementing the fixes). This makes it very easy to upgrade existing code. 

The DQMH online documentation has detailed info about the Validator:

http://delacor.com/documentation/dqmh-html/ValidatinganExistingDQMHModule.html