You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I need to enhance the event logic and the event dispatcher.
Right now, each class object, that implements an event function will receive the event, even if the event was not meant for that object.
f.e., if i have 2 SPAWN objects, SpawnA and SpawnB, and a crash event occurs of a unit belonging to SpawnA, then both SpawnA and SpawnB will receive the event.
However, DCS for certain (not all!) events include the UNIT name of the event.
I need to do a good analysis which events are related to units, and add event dispatchers for units, so that when the event is received within the dispatcher, it can immediately dispatch the event to the correct object that should receive the event, instead of letting each object decide if the event is for him...
This work can be done, but i want to encapsulate the event complexity by provide in the BASE class for each event type an API. So, this development will require some good analysis of the events being triggered by DCS in all possible scenarios, and then write an ecapsulation API around that in BASE.
Then, i need to REWORK in the class hierarchy of MOOSE the different event implementations to use the new API. So, i'll start with that and create a branch...
The text was updated successfully, but these errors were encountered:
I need to enhance the event logic and the event dispatcher.
Right now, each class object, that implements an event function will receive the event, even if the event was not meant for that object.
f.e., if i have 2 SPAWN objects, SpawnA and SpawnB, and a crash event occurs of a unit belonging to SpawnA, then both SpawnA and SpawnB will receive the event.
However, DCS for certain (not all!) events include the UNIT name of the event.
I need to do a good analysis which events are related to units, and add event dispatchers for units, so that when the event is received within the dispatcher, it can immediately dispatch the event to the correct object that should receive the event, instead of letting each object decide if the event is for him...
This work can be done, but i want to encapsulate the event complexity by provide in the BASE class for each event type an API. So, this development will require some good analysis of the events being triggered by DCS in all possible scenarios, and then write an ecapsulation API around that in BASE.
Then, i need to REWORK in the class hierarchy of MOOSE the different event implementations to use the new API. So, i'll start with that and create a branch...
The text was updated successfully, but these errors were encountered: