LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Actor Framework Packed Library dependency

Solved!
Go to solution

Hi,

 

I have build a Actor Framework project that works fine. For better maintenance I build packed Libs from different Actors like

setting, save data... This works also great.

 

The device Actor is dynamical loaded depending of the device type (PlugIN Architecture). I is also working correctly.

 

But because the Device class contains a lot of different children (devices). It is very big.

The goal is to septate the Low Level Device class into a few packed library.

The Development System would be much faster. And the EXE does not contain all PlugIn Devices. It should be possible

to put just the needed device into the Application.

 

But I don't now that is the best way to separate this actor into different Packed Libs.

Does any body have a idea?

 

Class hierarchy is attached.

 

 

0 Kudos
Message 1 of 2
(1,016 Views)
Solution
Accepted by topic author bodo_online

The solution is to implement a interface class between the real device and the actor.

This interface is not a child form the actor framework.

0 Kudos
Message 2 of 2
(972 Views)