Delacor Toolkits Documents

cancel
Showing results for 
Search instead for 
Did you mean: 

DQMH Feature Requests

Hello everyone,

 

We have been getting DQMH feature requests via this forum, via conversations during NI events and direct e-mail. We keep track of every suggestion in our internal tracking system, but we thought it would be a good idea to have a central location for others to add their own requests. Please create a different discussion for people to discuss your feature request and point to that entry in your post here.

 

We will add some of the ones we have already received. If you find a feature request you agree we should implement, please vote by clicking on the "Kudos" button for that post. Also, our CCFO (Cheap Chief Financial Officer) has asked us to add the following: "If you consider a feature to be particularly important, be sure to mail in your vote written on the back of a new US$100 bill. Multiple votes are, of course, allowed and encouraged" Smiley Wink

 

The more votes we receive for a particularly important feature, the more likely we are to implement it!

 

Best regards,

The Delacor team

 

Current feature requests:

 

Add a Rename Event utility to the Tools>>Delacor>>DQMH menu

Status: Done. Implemented in DQMH 3.0

 

Add a code to cloneable modules to make them behave as singletons

Status: Done. Implemented in DQMH 3.0

 

Add by default an error cluster in the Reply argument for Request & Wait for Reply Request Events

Status: Done. Implemented in  DQMH 3.0

 

Add Request events to TestStand insertion palette if TestStand is installed

Status: Won't implement.

 

Support DQMH Modules Templates when creating a new DQMH Module

Status: Done. Implemented in DQMH 3.0

in DQMH 4.0 added the option for these templates for them not have to be installed in the LabVIEW Data folder, instead, the metadata file can include a full path instead of a relative path.

Discussion:  DQMH first experience and a bit of a feature request

 

Add support for Real-Time or create a new DQMH module/project that would work on Real Time Targets

Status: Done. Implemented in DQMH 4.0

Discussion: Any caveats in using DQMH on Real Time

Module initialization with input from creator via Start Module

 

Remove the need for an argument when creating a new event

Status: Won't implement Implemented option to not have to add arguments in DQMH 3.0

Discussion: No arguments discussion

 

A way for the creator of a module to provide parameters for the Message Handler Initialize case

Status: Done. DQMH 2.1, we added a "code needed" bookmark with instructions inside Start Module.vi, so the developers would know where these initialization arguments if they needed to.

Discussion: Module initialization from Start Module and other ideas

 

A way to name modules/module clones during creation and then address them by name instead of by Module ID

Status: Wish List

Discussion: Module initialization from Start Module and other ideas

 

Requests with a To/From/Reply To header

Status: Wish List

Discussion: Module initialization from Start Module and other ideas

 

Floating Dialog Box for the Delacor Tools

Status: Wish List

Discussion: No discussion, the suggestion by K.Ross found further down in the comments to this document. If you want to discuss it further, feel free to start a new discussion.

 

Folder Cleanup

Status: Wish List

Discussion: No discussion, the suggestion by mRadziwon found further down in the comments in this document. If you want to discuss it further, feel free to start a new discussion.

 

Separate VI residing in each of DQMH_MESSAGE_CASES.

Status: Won't Implement

Discussion: No discussion, the suggestion by mRadziwon found further down in the comments in this document. If you want to discuss it further, feel free to start a new discussion.

 

Move sequence structure in Request and wait for reply to have access to merge errors

Status: Won't implement. The majority of DQMH developers remove the sequence structure anyway. It is there to facilitate scripting.

Discussion: No discussion, the suggestion by mRadziwon found further down in the comments in this document. If you want to discuss it further, feel free to start a new discussion.

 

Add the ability to choose the Icon Editor, currently only the default works. (I use Mark Balla's Icon editor.)

Status: Won't implement.

Discussion: No discussion, the suggestion by jdebuhr found further down in the comments in this document. If you want to discuss it further, feel free to start a new discussion.

 

Scripting API

Status: Wish List

Discussion: Scripting API

 

Combining the functionality of all 3 event types of DQMH

Status: Wish List

Discussion: suggestion by Barney10 found further down in the comments in this document. Also discussion available via Combining the functionality of all 3 event types of DQMH



Opportunity to learn form experienced developers / entrepeneurs (Steve and Joerg amongs 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?
Comments
Active Participant joerg.hampel Active Participant
Active Participant

+1 for the Request and Wait for Reply VI to output the cluster elements individually.

 

+1 for Darren's comment about the error. And by the way, I always rename the error in the cluster to just "Error" so the bundle by name in the MHL takes away less space.


An opportunity to learn from experienced developers / entrepreneurs (Fab and Steve amongst them):
DSH Pragmatic Software Development Workshops

CLAChampionCenter Of ExcellenceDQMH Trusted AdvisorWUELUG | ALA
Proven Zealot
Proven Zealot

I sometimes create Cloneable modules that I intend on usually calling as singletons. For these modules, I often manually update each request to have its Module ID input recommended (instead of required) and the Module ID default value of 0 (instead of -1). I also make the 'call as singleton' input on Start Module.vi have a default value of TRUE (instead of FALSE).

 

I'd like for there to be an option when creating a new cloneable module that says something like "optimize for calling as singleton" that would create the default requests as described above, and would also be tagged in some way so when I add new requests they will be created as described above.

DNatt, LV R&D
Active Participant Olivier-JOURDAN Active Participant
Active Participant

When I start a LabVIEW project based o DQMH, I would like to be able to create multiple modules (different name/type/icon/ (responsibility description <-- see previous request 😉 ) at once.

Olivier JOURDAN

Wovalab | Certified LabVIEW Architect |
Active Participant Olivier-JOURDAN Active Participant
Active Participant

It would be great to have an API that provides functions to :

  • list project DQMH modules (with /type/icon/ (responsibility description <-- see previous request 
     
     ) 
  • list request and broadcast for a module (with as many useful information that could be interesting to put in a project documentation 😉 )

As we are really close to Xmas (and I've been really nice all the year long), I would ask Santa to give me the 2 following additional functions :

  • for a request, which DQMH module is calling it
  • for a broadcast, which DQMH modules register it

Thank you in advance Santa 😉

 

Olivier JOURDAN

Wovalab | Certified LabVIEW Architect |
Active Participant joerg.hampel Active Participant
Active Participant

Add private events for helper loop 

 

This summarises / repeats doyle's feature request and Chris' feature request. Pleaase go there and give them kudos.

 

Seeing as the private request events would live in a "Private API" virtual subfolder, it'd be great if the tools (rename, delete event etc) would work with those too.


An opportunity to learn from experienced developers / entrepreneurs (Fab and Steve amongst them):
DSH Pragmatic Software Development Workshops

CLAChampionCenter Of ExcellenceDQMH Trusted AdvisorWUELUG | ALA
Proven Zealot
Proven Zealot

I would like a right-click plugin where I could right-click a DQMH broadcast subVI and "Find Event Frames". This would search all VIs in my current project for event structures that are registered for the broadcast event fired by the subVI I clicked on, and show me a list of results that I could double-click and be shown the event frames one at a time. Or I guess it could just open all the diagrams for me, since I probably want to walk through all of them anyway.

 

The operation could take a while, but would be worth it. I often find myself wondering where all the places are in my code that are registered for a particular broadcast.

DNatt, LV R&D
Contributors