DQMH Consortium Toolkits Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

Seeking best pratice to modify input of DQMH Event

Solved!
Go to solution

Hello,

 

I want to update inputs of a module Event (Request and wait for reply).

 

I am seeking for DO and DON'T on this specific operation. 

 

I would like to avoid deleting existing event and creating a new one... But may be you will tell me this is the only way.

 

Regards

0 Kudos
Message 1 of 8
(3,465 Views)
Solution
Accepted by topic author Behr-33

@Behr-33 wrote:

Hello,

 

I want to update inputs of a module Event (Request and wait for reply).

 

I am seeking for DO and DON'T on this specific operation. 

 

I would like to avoid deleting existing event and creating a new one... But may be you will tell me this is the only way.

 

Regards


Deleting and creating again is one option.

The other one is going to the module's Public API folder, there, you will see the Arguments folder. Find the typedef for the arguments that you want to change and modify it. Now, you need to make sure you modify the Request, and where the Event handles the request. Same for the reply. A way to do this is to right-click on the typedef on the project and select to find callers, go to each one of the callers and make sure the new elements are handled correctly.

 

I hope this helps.

 

Happy wiring, 

Fab

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 2 of 8
(3,436 Views)

Hello

 

It works ... and the operation enabled me to understand better DQMH framework: two birds with one stone

 

Thank you

 

Behr

Message 3 of 8
(3,406 Views)

Would be nice to have this as an action in the DQMH menu together with the create, rename etc. options.

0 Kudos
Message 4 of 8
(138 Views)

@Mads wrote:

Would be nice to have this as an action in the DQMH menu together with the create, rename etc. options.


What would you like that menu item to do? Let you select the module, then the event, and it will open the corresponding typedef and event VI for you so you can edit them?




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® (Developer Experience that makes you smile )


0 Kudos
Message 5 of 8
(112 Views)

Hi Joerg,

 

I wasn't the original requester, but I would imagine selecting the event, and then the "event arguments window" (and event payload if applicable) would open up with whatever data is already being used by that event. Then the data elements could be modified, and a scripting tool would go to the necessary places in the DQMH module to make sure the data can get to its final destination in the message handling loop.

0 Kudos
Message 6 of 8
(101 Views)

"What would you like that menu item to do? Let you select the module, then the event, and it will open the corresponding typedef and event VI for you so you can edit them?"

 

It would follow the model of the other event options, so yes it would ask you to select the module and event first, then let you edit it through a UI similar to the one you used when you configured the event in the first place.

If it was made specifically to only edit the argument it would just show the argument editing window as it appeared during event creation and you would then adjust it and everything would update accordingly.

0 Kudos
Message 7 of 8
(92 Views)

I agree that this would be a useful scripting tool. It's the #1 thing I've seen new DQMH developers trip up on once they get used to all the other scripting tools.

 

This idea has been proposed before on the DQMH Feature Requests page here. Although the idea is currently "Declined", I'm hoping the DQMH Consortium reconsiders and includes this feature in a future release.

Message 8 of 8
(86 Views)