So I have an actor that is responsible for a time critical high frequency DAQ task (Pulling data from a spectrometer), this actor has its own GUI where users can start and stop acquisition etc. From this actor I want to launch a nested actor that will be responsible for taking the acquired data and displaying it, doing some computations and saving to disk. The problem I am having is that if I set the new nested actor to inheret from the parent class that contains the DAQ task, then I have to have the parent implementation of this in the actor core of the nested actor, when really I just want the nested actor to act as all other actor cores and just handel messages as they arrive, not launch a duplicate of the actor core contatining the DAQ task.
Esentially I want the nested actor to have access to the parent class information that contains the DAQ task but to act as all other actor cores do, with the message handlong loop taking messages and processing them.
Any Ideas?
Thanks.