#306 fixed implementation according to feedback. To change between connecting lines and trajectories change a boolean constant in PostvisualizationRenderer.java

To activate the post visualization add a contacts.traj output file with TimestepPedestriansNearbyIdKey as key and a corresponding PedestriansNearby Processor with attribute printForPostVis set true

# Conflicts:
#	Scenarios/Demos/roVer/scenarios/mf_base.scenario
#	Scenarios/Demos/roVer/scenarios/mf_detailed.scenario
#	Scenarios/Demos/roVer/scenarios/mf_underground.scenario
#	Scenarios/Demos/roVer/scenarios/roVerTest001.scenario
#	Scenarios/Demos/roVer/scenarios/roVerTest002.scenario
#	Scenarios/Demos/roVer/scenarios/scenario001.scenario
#	Scenarios/Demos/roVer/scenarios/scenario002.scenario
#	Scenarios/Demos/roVer/scenarios/separation_slow_fast.scenario

extended supermarket


update scenario


before migration (V.1.11)


after migration to V1.12


adapted UnitTests TargetChangerController


adapted and extended unit tests


fixed bug


changed queue behavior manually

added a possibility to print the array of middle points for each contact, attribute is adjustable over json

added a tolerance for short leaves without breaking one constant contact, tolerance is adjustable over json

- it was already possible to write and rewrite values with putValue()
- it was already possible to clear the data with preLoop()
-> removeKey() doesn't allow any new functionality and exists solely for convenience and performance

In "15-Threat-ImitatingBehavior-SelfCatThreatModel.scenario", added another out-group member pedestrian

allows to add multiple Knowledge items to a pedestrian. These are
used to filter pedestrians based on some knowledge pedestrians have.

Optional source dependent PedestrianAttributes

See merge request !121