DQMH class wrapper - automated API to request creation?

[ConnerP]

So using DQMH as a wrapper around a(n abstract) class makes a lot of sense for things like HALs. However, one of the issues that irritates me is the code duplication. You want to call class:method.vi inside the DQMH and end up creating requests that mirror the class API just to feed the parameters into the DQMH for the class method call. This seems like a "dumb" operation that should have some level of automation. Is there a recommended way to make this process less repetitive? Thanks for your input.

[Ozfarmboy]

We just had to do the same thing here this week.  There is no automated way, but that doesn't mean it can't exist.

You should be able to use VI Scripting to analyse the terminals of the Public API of a given DQMH module, and automatically create class methods with the same terminals.

[bienieck]

Where can I find the underlying API used by the DQMH scripter? I'm mostly interested in the API used to generate new events (requests). I would like to automate the low level API wrapping as well.

[Ozfarmboy]

Make sure you have it enabled in options:

Then the VI scripting pallete is here:

[Olivier-JOURDAN]

You may also be interested in this palette the DQMH framework installs --> https://documentation.dqmh.org/dqmh/7.0/api.html#dqmh-scripting

[bienieck]

I'd like to explain in more detail what I'm trying to achieve. I want to programmatically execute the functionality provided by the "Create New DQMH Event" window, found under Tools»DQMH Consortium»DQMH»Events. Specifically, I want to provide parameters programmatically to generate the request, rather than going through the GUI manually each time.

I’m not looking to reinvent the wheel and write it with raw scripting VIs. Instead, I'd prefer to use the DQMH API directly, if possible. Any guidance on how to achieve this would be greatly appreciated. I don't see such an option in the DQMH Scripting Palette mentioned by Olivier. So, should I extract the code from the "Create New DQMH Event" window?

[joerg.hampel]

The Consortium does not provide official public documentation on that part of the DQMH scripting functionality, there is no API for this in the current version. I fear that extracting code will be tedious. The scripting VIs are password-protected, and we do not share the block diagrams (as stated in DQMH's license agreement).

I do agree though that this would be a handy thing to have, so please go ahead and post a feature request!

There's always the possibility of paying the Consortium to implement features (provided we agree with the feature's usefulness in the first place) if you can't wait for future releases. HSE just did this recently, and we'll talk about it once the next version of DQMH is released.

[bienieck]

Ok so here is my feature request if anyone is interested.

---

@joerg.hampel wrote:

There's always the possibility of paying the Consortium to implement features (provided we agree with the feature's usefulness in the first place) if you can't wait for future releases. HSE just did this recently, and we'll talk about it once the next version of DQMH is released.

---

I'll wait for now and see what is going to happen. In the end, I could try other, more open, frameworks (there may not be many of them but they are there).

[joerg.hampel]

Thanks for creating the feature request! You got my kudo... 😉