From 04:00 PM CDT – 08:00 PM CDT (09:00 PM UTC – 01:00 AM UTC) Tuesday, April 16, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

DQMH Consortium Toolkits Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

DQMH 7.0 feedback

First impressions are great. The new create event is a lot more sophisticated than what with had in DQMH 6.

Private requests, scripted helper loops, better file organization all checked! The custom broadcast payload practically allows us to convert a Request and Wait for Reply event to a Roundtrip. DQMH was already an invaluable help coding our projects but the new version certainly makes it even better! Congrats all the developers contributed to this release.

 

Some minor findings:

The Convert DQMH event dialog throws an error if you select a module which has no events to convert but you press OK. Doesnt seem to crash anything but the OK button might not be enabled if the event pulldown is empty.

 

Having a bigger initial block diagram on the module main is great. Is it possible / reasonable to also increase the API test block diagram?

 

There seems to be a big empty free label on the FP of the module mains. Is there a reason for that?

1984_0-1702112540703.png

 

The subdiagram label in the MHL loop is unreasonably big even if it doesnt even have any text inside. Is it possible to "size to text?" (this might not be releated to DQMH 7, maybe was like that in v6)

1984_1-1702112797037.png

 

Message 1 of 15
(1,178 Views)

Renaming a private request removes the cool new "private" icon from the VI's icon.

0 Kudos
Message 2 of 15
(1,103 Views)

All of the issues mentioned in this thread are currently covered by Issue #909 reported to the DQMH Consortium. Thanks for the feedback.

Message 3 of 15
(1,095 Views)

Hello 1984, a quick update:

 

  • The Convert DQMH event dialog throws an error if you select a module which has no events to convert but you press OK. Doesnt seem to crash anything but the OK button might not be enabled if the event pulldown is empty.
    • FIXED
  • Having a bigger initial block diagram on the module main is great. Is it possible / reasonable to also increase the API test block diagram?
    • NOT A BUG - this is something we'd want to get more buy-in for, perhaps with a Feature Request post?
  • There seems to be a big empty free label on the FP of the module mains. Is there a reason for that?
    • FIXED
  • The subdiagram label in the MHL loop is unreasonably big even if it doesnt even have any text inside. Is it possible to "size to text?" (this might not be releated to DQMH 7, maybe was like that in v6)
    • NOT A BUG - you cannot set 'Size to Text' on subdiagram labels
  • Renaming a private request removes the cool new "private" icon from the VI's icon.
    • FIXED

FIXED items will be published with the next release of DQMH.




DSH Pragmatic Software Development Workshops (Fab, Steve, Brian and me)
Release Automation Tools for LabVIEW (CI/CD integration with LabVIEW)
HSE Discord Server (Discuss our free and commercial tools and services)
DQMH® (The Future of Team-Based LabVIEW Development)


0 Kudos
Message 4 of 15
(999 Views)

Hi,

 

Today I have noticed that something odd is going on with the dependencies of my project. After couple hours of scratching my head I have found that probably these two items causing the problem:

1984_0-1704721111737.png

 

I'm positive that these get into the dependency list if you validate a DQMH module written in an earlier version and fix the error about the semaphores. This makes these two items showing up in the dependency list and as a side result the "Obtain module Semaphore.vi" of the module is not called by anybody anymore.

 

I dont know whats going on in the background and I dont know if this is a but but it definitely gave me a headache, cause I thought I did something wrong. 

 

 

0 Kudos
Message 5 of 15
(966 Views)

@1984, if you could DM me a simple project that reproduces the issue, or alternatively give me exact steps to reproduce the issue, I can submit a Bug report to the DQMH Consortium to investigate further.

0 Kudos
Message 6 of 15
(954 Views)

I'll be off the grid for this week so can't do it anytime soon, but just take a module written in DQMH6.0 (could be simply the stock singleton module), validate and fix the listed issues under DQMH7.0

 

That - for me - added that dependency to the project. Let me know if you could / couldn't reproduce the issue. If not I'll get back to this once I'm back.

0 Kudos
Message 7 of 15
(947 Views)

Thanks @1984. I've filed Issue #912 to the DQMH Consortium on the 'stub' VIs in Dependencies issue. If you end up being able to share more details about the issue, please post them here.

0 Kudos
Message 8 of 15
(940 Views)

I add a new panel module based 7.0.0.128, but it doesn't work well. During debugging I found that it fail to sync modules.2024-01-11_17h24_21.png

0 Kudos
Message 9 of 15
(905 Views)

@lbc898 wrote:

I add a new panel module based 7.0.0.128, but it doesn't work well. During debugging I found that it fail to sync modules.


There are some known issues with the Panel Manager (which was written with DQMH 3.1) and the latest DQMH Validation tools. These issues are being tracked by the DQMH Consortium as Issue #901.

0 Kudos
Message 10 of 15
(886 Views)