GitLab

- removed obsolete and duplicate modular movement classes (check your
config-files, you might need to replace "modular" with "modularosm" in
some cases

Nodes are placed on random positions on the connection lines between Attraction points instead of a complete random position.

+ Add possibility to draw rectangular areas in the visualisation. Data of all nodes inside this geofence will be combined visualized
+ Add another factor when calculating the hesitation time for the DRASMobileComponents to factor in the time the node already waited.

+ Maps are now displayed when using local analysing

- set target for movement currently only supported in the modularosm
model, feel free to extend other models by overwriting the default
implementation and create the corresponding merge requests.

- support for in-model placement of nodes

- deprecated MovementSupported
- used LocationSensor and LocationActuator
- decoupled nested listener structures used within the old models

fix transition strategy to only fire once an Attraction Point is reached
remove POI limitation for Json-based Attraction Points

enabled direct instantiation of custom attraction points in the XML
config

- Prior, moving at a certain speed towards a target position could lead
to overshooting and, thus, to oscillations.

- Refactored data scaling to adhere to the world dimensions specified in
meters
- Scaling of UI elements is now done in a unified fashion by the
VisualizationInjector

and max for one component. 
Models MAY set a new speed as they wish (api of MovementSupported
changed to allow this behavior). Can be used, e.g., to update speed once
a target waypoint has been reached.

Martin Hellwig authored Jul 16, 2015 and Björn Richerzhagen committed Oct 27, 2015

Added two classes to visualize images as background. One loads background-images at runtime; Also runtime-loading of POIs are now possible

Added two classes to visualize images as background. One loads background-images at runtime; Also runtime-loading of POIs are now possible