I’d like to suggest making the DQMH scripting tools API public. This would allow new events or modules to be generated programmatically.
My use case: I’d like to take any non-DQMH library and generate a DQMH layer for the library’s public API. With some clever coding and discipline, this could automate the creation of a TestStand API based on DQMH, which would be incredibly useful.
Moreover, public APIs often encourage the development of supporting tools and promote the technology, especially within creative communities.
Michał Bieńkowski
CLA, CTA, CPI
- Did someone devote their time to help solve your problem? Appreciate it and give kudos.
- Problem solved? Accept as a solution so that others can find it faster in the future.
- Contribute to the development of TestStand by voting on the TestStand Idea Exchange.
After consideration and discussion, we decided to decline this feature request.
We fear it would be very difficult to maintain and document. It also would increase the workload for future release making sure nothing breaks. Scripting Hooks are available as a potential alternative.
We really appreciate your input, declining the idea does not mean it didn't help us fine-tune the scope of DQMH and reconsider our strategy. Please keep those ideas coming 😉