Hi everybody, I have some trouble, finding the best solution to use the API from a dqmh module in a plugin. I have two modules, let's call it A and B. A is the mainmodule and starts and controls module B. Because there are so many different and yet undefined programmsequences who will be executed in module A, we decided to implement a plugin structure there. With this structure we will be able to outsource all this different programmsequences and can replace them, without touching the module A. Because of this decision, the plugins need the API of module B as well to communicate with this. Most of the the time, there is more than one module loaded but they running all sequential. Ways that are not working 🙂 using the API in the plugins because the LV compiler will build the module B in every ppl .. Ideas: Build module B as ppl, start the module B.lvlibp from module A and use the API in the plugins as consequence, module B.lvlibp has to be in the same directory like the plugins Build a "interface" for all the API events, while loading and intitalizing the plugin pass the event references to the plugin and use it. Create a "dummy" API and work on the passed references in my opinion this is error prone and lot of double coding Are there some experiences or best practices to handle this or are there some other ideas from the community to help to solve my problem? Many thanks in adance Matthias

Check out the presentation that Matthias Baudot made at GDevCon 1 or the one at NI Week, he shows a demonstration on how to package DQMH into a ppl for a plugin architecture. Go to http://bltforlabview.com and go to the Conferences tab. Regards, Fab

DQMH Consortium Toolkits Discussions

Best practice when using an DQMH API in PPL Plugins

Solved!

I got some idea about it but still need some basic example or video for using dqmh module as ppl.

Message 11 of 11

(28 Views)

DQMH Consortium Toolkits Discussions

Best practice when using an DQMH API in PPL Plugins

Re: Best practice when using an DQMH API in PPL Plugins