07-29-2018 06:06 PM
Thanks, that is helpful to see. I think I had most of it right. The part that isn't clear to me is sending an event...you would need to send the entire cluster, empty, except for the data you want to send? Does that generate any overhead?
07-29-2018 06:26 PM - edited 07-29-2018 06:31 PM
In your Stop Core case, you have your Generate Event and Destroy Event cascaded...does that create a possible situation where the event is destroyed prior to the event being handled? I simply don't know. To manage that, I made it so that the stop UE is destroyed in Actor Core after the event structure is stopped. The rest of the UE are destroyed in the Stop Core as you indicated though.
For Stop Core, I was trying to use Cluster to Array, but I guess there is no common datatype for the UE references to be cast to...unless there is perhaps another way of achieving that.
07-29-2018 07:47 PM
Just unbundle the one particular event you are interested in sending and send that one particular event.
07-29-2018 07:51 PM
As far as firing the stop event and then closing it, that is what NI teaches in their class and it seems to work. Destroying the event ref simply destroys the ability to generate another event, but the event queue created by the register events (in Actor core) will still handle the stop event. Hope that is clear.
07-29-2018 07:54 PM
Yes, I think I understand. Thanks!
08-01-2018 09:20 AM
08-01-2018 09:39 AM
@paul.r wrote:
https://bitbucket.org/composedsystems/mva-framework/src/master/
FYI
Taking a look, thanks!
08-01-2018 12:06 PM
The Framework looks very interesting, through it is reminiscent of when I was looking for C#/WPF MVVM examples and frameworks 😛 I think I need to bash away at a lower level first to learn a few things. I looked at the example block diagrams, and while I could understand at a high level what it was doing, I have no idea how to implement something similar on my own.