Hot off the press: DQMH v7.1.1

[joerg.hampel]

You can find all packages of our latest release on VIPM.io and in your VI Package Manager.

New Features

1. MD5 checksum for all VIPs and the VIPC (Issue #1009)
   • This feature comes from carlos_camargo's request
   • You can find the MD5 signatures on our Releases download page

Fixes

1. The instructions in the Create New DQMH Event tool are now correctly displayed on some systems using specific fonts. (Issue #1002)
2. The Duplicate event tool is no longer closing references before executing post-script plugins. This allows you to use those references in the post-scripting plugin VIs called after this tool’s execution. (Issue #1003)
3. The creation of a Private Local Event is now more robust. (Issue #1006)

4. The Rename Event and Remove Event tools are now supporting the new arrangement in the Private Event cluster introduced in v7.1.0. (Issue #1007)

You can always find the full list of changes in the Release Notes. 

This release has a special meaning to us: We've been working relentlessly on our workflows and our CI pipelines to make sure we're able to release hot fixes in a very timely fashion. Documentation is written as we implement features and fixes, and automation takes care of the complete build and release process. We're proud!!

With lots of love,

your Consortium

[adkin]

Can't wait to try it out! Thank you to the entire Consortium for all of their hard work!

Is there any way to view the details of the Issues listed? Seems like at least some of them are internal with no way to know what they fix exactly.

Specifically, I'm interested in Issue #1006 to know if it addresses my recent post: Private Local Request Bug in DQMH 7.1.0 

Thanks,

Aaron

[joerg.hampel]

Hey adkin,

thanks for the kind words, and for taking the time to reach out (and for the elaborate description in your other, related post)!

At this time, the issue tracker is not available to the general public. I can see that in this case it would have been handy. Sadly, issue #1006 does not deal with the phenomenon you're seeing...

We're investigating the behaviour you reported, I'll get back to you on the other thread.