AssignRouteAction - shared control strategy
When adapting the AssignRouteAction
for the upcoming generated engine, we saw that all entities get the same shared_ptr to a single control_strategy (member of the class) which means, that changes of a single control strategy will affect other entities as well. While this shall not happen anyhow, the questions are if (A) the interface is sufficient fortified (pushing vectors of shared_ptrs to the simulator), if (B) this intended behavior, or (C) I overlooked something ;)
Any thoughts? @arauschert